aboutsummaryrefslogtreecommitdiffstats
path: root/docs/development/devtools/policy-participant-smoke.rst
diff options
context:
space:
mode:
authorlapentafd <francesco.lapenta@est.tech>2022-04-12 11:23:22 +0100
committerlapentafd <francesco.lapenta@est.tech>2022-04-12 12:17:54 +0100
commit45ce655d0a7a1568e3518bc968f968a41688f99d (patch)
treecb952120e4bbef766e296969834f77963f389333 /docs/development/devtools/policy-participant-smoke.rst
parent4236d55e6df1c17318995a65ad0a6e9411462456 (diff)
Fix typos in policy docs devtools
Update images names, that were not displaying Issue-ID: POLICY-3941 Signed-off-by: lapentafd <francesco.lapenta@est.tech> Change-Id: I85115478f285028ad02644614bee9c0f7f178206
Diffstat (limited to 'docs/development/devtools/policy-participant-smoke.rst')
-rw-r--r--docs/development/devtools/policy-participant-smoke.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/development/devtools/policy-participant-smoke.rst b/docs/development/devtools/policy-participant-smoke.rst
index bf236351..031c2cb3 100644
--- a/docs/development/devtools/policy-participant-smoke.rst
+++ b/docs/development/devtools/policy-participant-smoke.rst
@@ -13,7 +13,7 @@ The Smoke testing of the policy participant is executed in a local CLAMP/Policy
2. Setup Guide
**************
-This section will show the developer how to set up their environment to start testing in GUI with some instruction on how to carry out the tests. There are a number of prerequisites. Note that this guide is written by a Linux user - although the majority of the steps show will be exactly the same in Windows or other systems.
+This section will show the developer how to set up their environment to start testing in GUI with some instruction on how to carry out the tests. There are several prerequisites. Note that this guide is written by a Linux user - although the majority of the steps show will be exactly the same in Windows or other systems.
2.1 Prerequisites
=================
@@ -305,7 +305,7 @@ To perform the Smoke testing of the policy-participant we will be verifying the
Creation of ACM:
************************
-A ACM is created by commissioning a Tosca template with ACM definitions and instantiating the ACM with the state "UNINITIALISED".
+An ACM is created by commissioning a Tosca template with ACM definitions and instantiating the ACM with the state "UNINITIALISED".
Using postman, commission a TOSCA template and instantiate using the following template:
:download:`Tosca Service Template <tosca/tosca_service_template_pptnt_smoke.yaml>`