From 16ec88e1a6fbd9ea1e9ab51c908db87b595e10df Mon Sep 17 00:00:00 2001 From: JakobKrieg Date: Mon, 9 Nov 2020 20:10:42 +0100 Subject: PNF simulator guide fix postman collections, typos Issue-ID: CCSDK-2970 Change-Id: I22c576cae3b1ad69c3dcc117f9ede33a0c578cb7 Signed-off-by: JakobKrieg --- docs/usecases/pnf-simulator.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/usecases/pnf-simulator.rst') diff --git a/docs/usecases/pnf-simulator.rst b/docs/usecases/pnf-simulator.rst index 4be95113a..3712253ee 100644 --- a/docs/usecases/pnf-simulator.rst +++ b/docs/usecases/pnf-simulator.rst @@ -9,7 +9,7 @@ PNF Simulator Day-N config-assign/deploy Overview ~~~~~~~~~~ -This use case shows in a very simple how the day-n configuration is assigned and deployed to a PNF through CDS. +This use case shows in a very simple way how the day-n configuration is assigned and deployed to a PNF through CDS. A Netconf server (docker image `sysrepo/sysrepo-netopeer2`) is used for simulating the PNF. This use case (POC) solely requires a running CDS and the PNF Simulator running on a VM (Ubuntu is used by the author). @@ -456,7 +456,7 @@ For creating day-2 configuration call the same endpoint and use the following pa **Config-Deploy:** Now we will make the CDS REST API calls to push the day-1 and day-2 configuration changes to the PNF simulator. -Call the same `process` endpoint with the following payload: +Call the same endpoint `process` with the following payload: .. code-block:: JSON -- cgit 1.2.3-korg