Commit 739b6031 authored by Daniel García's avatar Daniel García
Browse files

Fix typos

parent 6044d5ae
Loading
Loading
Loading
Loading
+9 −9
Original line number Diff line number Diff line
@@ -58,7 +58,7 @@ Within the `provider_folder`, the SDK will store some folders named with the pro
### Provider onboarding

CAPIF SDK references:
* **CAPIF SDK function**: <mark>onboard_provider()</mark>\
* **CAPIF SDK function**: <mark>onboard_provider()</mark>
* **CAPIF SDK script**: <mark>provider_capif_connector.py</mark>

SDK simplifies the onboarding process for Provider developers. It also provides the capability to register several APFs and AEFs if necessary.
@@ -72,7 +72,7 @@ Using Publish Service it is required to fulfill certain fields of the [capif-sdk
### Services publishing

CAPIF SDK references:
* **CAPIF SDK function**: <mark>publish_services()</mark>\
* **CAPIF SDK function**: <mark>publish_services()</mark>
* **CAPIF SDK script**: <mark>provider_publish_api.py</mark>

SDK simplifies the process of publishing an API in CAPIF. Besides, it also provides the ability to chose which APF and AEFs will be used to publish the API.
@@ -86,7 +86,7 @@ It is mandatory to be [onboarded as a provider](#onboard_provider--script-provid
### Services deletion

CAPIF SDK references:
* **CAPIF SDK function**: <mark>unpublish_service()</mark>\
* **CAPIF SDK function**: <mark>unpublish_service()</mark>
* **CAPIF SDK script**: <mark>provider_unpublish_api.py</mark>

SDK simplifies the process of deleting an API available in CAPIF.
@@ -101,7 +101,7 @@ It is mandatory to have onboarded as a [provider](#onboard_provider--script-prov
### Services update

CAPIF SDK references:
* **CAPIF SDK function**: <mark>update_service()</mark>\
* **CAPIF SDK function**: <mark>update_service()</mark>
* **CAPIF SDK script**: <mark>provider_update_api.py</mark>

SDK simplifies the process of updating an API already registered at CAPIF. It also supports selecting which APF and AEFs will be used to update the API.
@@ -116,7 +116,7 @@ It is mandatory to have onboarded as a [provider](#onboard_provider--script-prov
### Get services

CAPIF SDK references:
* **CAPIF SDK function**: <mark>get_service()</mark>\
* **CAPIF SDK function**: <mark>get_service()</mark>
* **CAPIF SDK script**: <mark>provider_get_published_api.py</mark>

SDK simplifies the process of receiving the information of one service published previously in published-apis.json
@@ -130,7 +130,7 @@ It is mandatory to have onboarded as a [provider](#onboard_provider--script-prov
### Get all services

CAPIF SDK references:
* **CAPIF SDK function**: <mark>get_all_services()</mark>\
* **CAPIF SDK function**: <mark>get_all_services()</mark>
* **CAPIF SDK script**: <mark>provider_get_all_published_api.py</mark>

SDK simplifies the process of receiving the information of all available services published previously in published-apis.json
@@ -169,7 +169,7 @@ Within the `invoker_folder`, the SDK will store some folders named with the prov
### Onboarding process

CAPIF SDK references:
* **CAPIF SDK function**: <mark>onboard_invoker()</mark>\
* **CAPIF SDK function**: <mark>onboard_invoker()</mark>
* **CAPIF SDK script**: <mark>invoker_capif_connector.py</mark>

Simplifies the process of onboarding for Invoker users
@@ -179,7 +179,7 @@ Simplifies the process of onboarding for Invoker users
### Discover process

CAPIF SDK references:
* **CAPIF SDK function**: <mark>discover()</mark>\
* **CAPIF SDK function**: <mark>discover()</mark>
* **CAPIF SDK script**: <mark>invoker_service_discover.py</mark>

In this functionality, [discover_filter](./sdk-configuration.md) is used to retrieve the access of target API specified in discover filter.
@@ -195,7 +195,7 @@ DISCLAIMER: if it's the first time the user runs discover() it will appear a war
### Obtain Invoker tokens

CAPIF SDK references:
* **CAPIF SDK function**: <mark>get_tokens()</mark>\
* **CAPIF SDK function**: <mark>get_tokens()</mark>
* **CAPIF SDK script**: <mark>invoker_service_get_token.py</mark>

This functionality simplifies the process of creating a security context based on JWT tokens in CAPIF, allowing to access the target APIs.