summaryrefslogtreecommitdiffstats
path: root/docs/development/devtools/policy-participant-smoke.rst
diff options
context:
space:
mode:
authorLiam Fallon <liam.fallon@est.tech>2022-04-13 08:43:36 +0000
committerGerrit Code Review <gerrit@onap.org>2022-04-13 08:43:36 +0000
commit977a81da2257629a1fa54515578d3773f934f12f (patch)
tree25090e8538f7bf836202d0232d539d232a1a465e /docs/development/devtools/policy-participant-smoke.rst
parentec1d537663eea6764322993c4bbc684c984fceb2 (diff)
parent45ce655d0a7a1568e3518bc968f968a41688f99d (diff)
Merge "Fix typos in policy docs devtools"
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>`