Fix intros.

As explained before, OpenCAPIF SDK is designed to play two different roles:

- [Provider NetApp](#provider-netapp)

    - [Important Information for Provider](#important-information-for-provider-consumer)

    - [Important information for Providers](#important-information-for-provider-consumer)

    - [Onboard Provider](#onboard_provider--script-provider_capif_connectorpy)

    - [Publish Services](#publish_services--script-provider_publish_apipy)

    - [Unpublish Services](#unpublish_service--script-provider_unpublish_apipy)

    - [Update Services](#update_service--script-provider_update_apipy)

    - [Get Published Services](#get_service--script-provider_get_published_apipy)

    - [Get All Published Services](#get_all_services--script-provider_get_all_published_apipy)

    - [Update and Offboard Provider](#update_provider-and-offboard_provider--provider_capif_connector_updatepy-and-provider_capif_connector_offboardingpy)

    - [Publish services](#publish_services--script-provider_publish_apipy)

    - [Unpublish services](#unpublish_service--script-provider_unpublish_apipy)

    - [Update services](#update_service--script-provider_update_apipy)

    - [Get published services](#get_service--script-provider_get_published_apipy)

    - [Get all published services](#get_all_services--script-provider_get_all_published_apipy)

    - [Update and offboard Provider](#update_provider-and-offboard_provider--provider_capif_connector_updatepy-and-provider_capif_connector_offboardingpy)

- [Invoker NetApp](#invoker-netapp)

    - [Important Information for Invoker](#important-information-for-invoker-consumer)

    - [Important information for Invokers](#important-information-for-invoker-consumer)

    - [Onboard Invoker](#onboard_invoker--script-invoker_capif_connectorpy)

    - [Discover API](#discover--script-invoker_service_discoverpy)

    - [Get Tokens](#get_tokens--script-invoker_service_get_tokenpy)

    - [Update and Offboard Invoker](#update_invoker-and-offboard_and_deregister_invoker--invoker_capif_connector_updatepy-and-invoker_capif_connector_offboardingpy)

    - [Get tokens](#get_tokens--script-invoker_service_get_tokenpy)

    - [Update and offboard Invoker](#update_invoker-and-offboard_and_deregister_invoker--invoker_capif_connector_updatepy-and-invoker_capif_connector_offboardingpy)

- [Other Features](#other-features)

    - [Register and Login](#script-register_and_loginpy)

    - [Deregister and Login](#script-deregister_and_loginpy)

## Important information for Provider consumer

In the `provider_folder`, it will be located several folders with each `capif_username` that has onboarded as a provider, for each folder it is created by SDK this files:

Within the `provider_folder`, the SDK will store some folders named with the provided `capif_username` it has been previously registered from CAPIF administrator. At each folder, there will be found the following files:

- `capif_provider_details.json` : Contains all the APFs and AEFs ids that have already onboarded with this capif_username

- `CAPIF_<api_name><_API_id>.json` : If it's already published or updated an API, It will be available a copy of the last payload.

# Invoker NetApp

The common path to follow using CAPIF in order to get an API token of the service it's wanted to use is by following this steps:

## Important information for Invoker consumer

In the `invoker_folder`, it will be located several folders with each `capif_username` that has onboarded as a provider. For each folder, it could be found:

Within the `invoker_folder`, the SDK will store some folders named with the provided `capif_username` it has been previously registered from CAPIF administrator. At each folder, there will be found the following files:

-   `capif_api_security_context_details.json`: This file contains the information of the invoker. It will contain: