From 9e0a8433cc033ee08a7034b69ef62ad18a768d3b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20Garc=C3=ADa?= <daniel.garciasanchez@telefonica.com>
Date: Wed, 25 Sep 2024 12:52:36 +0200
Subject: [PATCH] Update doc format

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 936a25d..68a8487 100644
--- a/README.md
+++ b/README.md
@@ -119,14 +119,14 @@ A NetApp development running as a Provider would typically follow this process s
       provider = CAPIFProviderConnector(config_file=utilities.get_config_file())
     ```
 
-2. **Onboard the Provider:**
+2. **Onboard the Provider:** \
     Register the provider with the CAPIF system to enable the publication of APIs:
 
     ```python
       provider.onboard_provider()
     ```
 
-3. **Prepare API details:**
+3. **Prepare API details:** \
    Locate the provider API details in the username folder. Choose the APF (Application Programming Function) and AEFs (Application Enabling Functions) identifiers, and fulfill the publish_req structure and the api_description_path:
 
 <p align="center">
@@ -134,7 +134,7 @@ A NetApp development running as a Provider would typically follow this process s
   <img src="./doc/images/publish_req-example.png" alt="config-example"  width="400"/>
 </p>
 
-4. **Publish the services:**
+4. **Publish the services:** \
    Use the publish_services() method to register the APIs with the CAPIF framework:
 
     ```python
-- 
GitLab