Fix doc config files and dead links

[policy/parent.git] / docs / development / devtools / policy-gui-acm-smoke.rst

diff --git a/docs/development/devtools/policy-gui-acm-smoke.rst b/docs/development/devtools/policy-gui-acm-smoke.rst
index 8070204..cd60019 100644 (file)
--- a/docs/development/devtools/policy-gui-acm-smoke.rst
+++ b/docs/development/devtools/policy-gui-acm-smoke.rst
@@ -3,7 +3,7 @@
 .. _clamp-gui-acm-smoke-tests:
 
 CLAMP GUI Smoke Tests
----------------------------
+---------------------
 1. Introduction
 ***************
 The CLAMP GUI for Automation Compositions is designed to provide a user the ability to interact
@@ -20,7 +20,7 @@ This document will serve as a guide to do smoke tests on the different component
 
 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. The IDE used in the examples here is Intellij but most or all of what is described should be the same across IDEs.
+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. The IDE used in the examples here is Intellij but most or all of what is described should be the same across IDEs.
 
 2.1 Prerequisites
 =================
@@ -181,7 +181,7 @@ To start the acm runtime we need to go the "runtime-acm" directory in the clamp
 
 2.3.8 Automation Composition GUI
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-At this point, all of the components required to test out the acm gui are running.We can start to make changes, and have those changes reflected in the UI for immediate feedback on our changes. But first, we must run the GUI.
+At this point, all of the components required to test out the acm gui are running. We can start to make changes, and have those changes reflected in the UI for immediate feedback on our changes. But first, we must run the GUI.
 
 Firstly, go to the GUI repo and navigate to "gui-clamp/ui-react". To setup for development, we must install the dependencies of the GUI. We can do this using the npm package manager. In the directory, simply run:
 
@@ -195,7 +195,7 @@ This will trigger installation of the required packages. The application is conf
 
     npm start
 
-This uses nodes internal test dev web server to server the GUI. Once started, you can navigate to the server at "https://localhost:3000" and login with "admin/password".
+This uses nodes internal test dev web server to server the GUI. Once started, you can navigate to the server at "localhost:3000" and login with "admin/password".
 
 That completes the development setup of the environment.
 
@@ -264,7 +264,7 @@ and
 
 .. image:: images/gui/PolicySuccess.png
 
-Following the same procedure as changeing the state to PASSIVE, we can then change to UNINITIALISED. This deletes the policies and policy types through the policy api and changes the overall state of the loop. we can then delete it from the Manage Instances table by clicking on Delete.
+Following the same procedure as changing the state to PASSIVE, we can then change to UNINITIALISED. This deletes the policies and policy types through the policy api and changes the overall state of the loop. we can then delete it from the Manage Instances table by clicking on Delete.
 
 Decommissioning
 ===============