summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorPamela Dragosh <pdragosh@research.att.com>2018-04-26 18:32:15 +0000
committerGerrit Code Review <gerrit@onap.org>2018-04-26 18:32:15 +0000
commit9562f3b5dfc5613629b5119cb629c81005d93431 (patch)
tree00f93d2528964b7728adfc314bfc333b4eaedd01 /docs
parent37eebe9e6c814e4756443bf9d6f10afe9954aef6 (diff)
parent7d861e6c07d725df4518f75fc187c0be02592db9 (diff)
Merge "Fix typo in documentation"
Diffstat (limited to 'docs')
-rw-r--r--docs/platform/clsimulation.rst2
-rw-r--r--docs/platform/deployPDPPAP.rst4
2 files changed, 4 insertions, 2 deletions
diff --git a/docs/platform/clsimulation.rst b/docs/platform/clsimulation.rst
index 3a9f4342b..b24e72d03 100644
--- a/docs/platform/clsimulation.rst
+++ b/docs/platform/clsimulation.rst
@@ -30,7 +30,7 @@ Alternatively, this command could be used:
curl --silent --user <userName>:<password> -X PUT --header "Content-Type: text/plain" –data @<onsetFile> http://localhost:9696/policy/pdp/engine/topics/sources/ueb/<topic>/events
-The topic beeing used is *unauthenticated.DCAE_CL_OUTPUT*, which is subject to change. The onset file is a file that contains the data to inject as the onset. The data contained depends on the use case. This is an example for VoLTE:
+The topic being used is *unauthenticated.DCAE_CL_OUTPUT*, which is subject to change. The onset file is a file that contains the data to inject as the onset. The data contained depends on the use case. This is an example for VoLTE:
.. code-block:: json
:caption: VoLTE_Sample_Onset
diff --git a/docs/platform/deployPDPPAP.rst b/docs/platform/deployPDPPAP.rst
index 476d6860b..a04515899 100644
--- a/docs/platform/deployPDPPAP.rst
+++ b/docs/platform/deployPDPPAP.rst
@@ -106,7 +106,9 @@ Healthcheck / Testing
- The Policy PDP health check can be checked using the generic procedure documented above for PAP which applies to all policy components.
-* Apart from the above check PDP also provides the swagger UI from which PDP REST APIs which can be tested and used, this also lets us know the PDP Status. In order to access PDP's swagger UI visit http://{PDP_URL}:8081/pdp/swagger-ui.html
+- Apart from the above check PDP also provides the swagger UI from which PDP REST APIs which can be tested and used, this also lets us know the PDP Status. In order to access PDP's swagger UI visit ``http://{PDP_URL}:8081/pdp/swagger-ui.html.``
+
+- Apart from the above check PDP also provides the swagger UI from which PDP REST APIs which can be tested and used, this also lets us know the PDP Status. ``In order to access PDP's swagger UI visit http://{PDP_URL}:8081/pdp/swagger-ui.html.``
- In order to test the Policy components, the swagger UI provided by PDP can be used to test PDP and PAP.