Merge "Correction to documentation guide for API"
diff --git a/docs/guides/onap-developer/how-to-use-docs/api-swagger-guide.rst b/docs/guides/onap-developer/how-to-use-docs/api-swagger-guide.rst
index d5e2099..9d3a7f6 100644
--- a/docs/guides/onap-developer/how-to-use-docs/api-swagger-guide.rst
+++ b/docs/guides/onap-developer/how-to-use-docs/api-swagger-guide.rst
@@ -16,7 +16,8 @@
A Swagger editor is available here `<http://editor.swagger.io/>`_ to generate
such JSON files.
-As a result, you should get one JSON file per API:
+As a result, you should get one JSON file per API. For example the project
+**my** has 2 API: **myAPI1** and **myAPI2**.
- myAPI1.json
- myAPI2.json
@@ -35,17 +36,28 @@
"myAPI1", ":download:`link <myAPI1.json>`"
"myAPI12", ":download:`link <myAPI2.json>`"
+.. note::
+ During documentation merge/publish at RTD, any file referenced in an RST file with
+ ':download:' and relative path to a contributing project repository is copied, uniquely
+ named, and published with the generated HTML pages.
The code is available here:
.. code:: rst
- ..csv-table::
- :header: "API name", "Swagger JSON"
- :widths: 10,5
+ .. csv-table::
+ :header: "API name", "Swagger JSON"
+ :widths: 10,5
- "myAPI1", ":download:`link <myAPI1.json>`"
- "myAPI2", ":download:`link <myAPI2.json>`"
+ "myAPI1", ":download:`link <myAPI1.json>`"
+ "myAPI2", ":download:`link <myAPI2.json>`"
+
+.. note::
+ The syntax of <myAPI1.json> is to be taken literally. Keep '<' and '>'.
+
+.. note::
+ Note the “v” in swaggerv2doc!
+ If your JSON file has multiple endpoints, this directive does not preserve the order.
API Swagger
-----------