some minor changes to make the content better

modules/LABENV/pages/index.adoc

@@ -4,9 +4,15 @@
 
 . **Log in** to the xref:#RHDP-Portal-Links[RHDP portal].
 . **Search** for the catalog entry: **Advanced Deployment of Ansible Automation Platform 2.5**.
++
+image::1.png[]
+
 . **Click** on the catalog entry in the search results.
 . On the catalog page, **click** the **Order** button.
 . **Fill out** the required details in the order form.
++
+image::form.png[]
+
 . **Review the warning** at the bottom of the form and **check the box** labeled: +
    *“I confirm that I understand the above warnings.”*
 . **Click** the **Order** button to place your lab order.

modules/chapter1/pages/section2.adoc

@@ -8,7 +8,12 @@ The important part is how to make connections between the nodes which is also kn
 
 Let us create an example of 2 Deployment structures which will help you understand the above concept better: 
 
+
 . Creating a simple 1 controller node connected to the 1 execution node with 1 Unified UI node and the database nodes is mandatory to have. So the below example only shares the information related to that. 
++ 
+image::2.png[]
++
+Ansible automation platform in the above had nodes Automation Controller/execution, Unified UI and Database.
 
 [source,bash,role=execute]
 ----
@@ -26,6 +31,8 @@ execution_hostname.example.com
 In the above example we can see that there is 1 Automation Controller node mentioned as a node_type= control which acts as a control node to execute jobs on the execution nodes. 
 
 . Creating a 1 hop node and 1 execution node connected to the hop node and the other execution node directly connected to the Automation Controller node.
++ 
+image::2.1.png[]
 
 [source,bash,role=execute]
 ----
@@ -39,17 +46,17 @@ peers=execution
 [execution_nodes]
 execution_hostname1.example.com peers=proxy
 execution_hostname2.example.com
+execution_hop.example.com node_type=hop
 
 
 [execution]
 execution_hostname2.example.com
 
 [proxy:vars]
-node_type=hop
 peers=automationcontroller
 
 [proxy]
-execution_hostname1.example.com
+execution_hop.example.com
 ----
 
 The `execution_nodes` group helps the AAP installer script to understand how to install software to make that node work as an execution node for the AAP and the `[execution]` group will tell the script about the peering and how it needs to be done to the automation controller. 
@@ -77,4 +84,4 @@ execution_hostname2.example.com
 hop_hostname2.example.com receptor_type=hop receptor_peers='["execution_hostname2.example.com"]'
 ----
 
- NOTE: The execution and hop concept remains the same only the deployment will be different  as you have to use receptor_type to define the hop node and The Containerized installer for have node_type as hybrid only for the Automation Controller.
+ NOTE: The execution and hop concept remains the same only the deployment will be different as you have to use receptor_type instead of node_type.

modules/chapter1/pages/section3.adoc

@@ -11,8 +11,7 @@ video::advanced-aap-2.5.mp4[align="left",width=800,height=500]
  $ sudo dnf install -y wget git-core rsync vim ansible-core
 ----
 
-. Copy the content of the into a notepad locally the `/home/devops/inventory`. 
-// Copy the content of???
+. Copy the content of the `inventory` into a notepad locally the `/home/devops/inventory`. 
 +
 [source,bash,role=execute]
 ----
@@ -90,3 +89,13 @@ aap2.g8hpb.sandbox3274.opentlc.com
 . Provide the *Red Hat login ID* to get the subscription for attaching it to the AAP and a *60-day subscription to Red Hat Ansible® Automation Platform* or *Red Hat Developer Subscription for Individuals* subscription can be used for this lab.
 
 . After *Login* run the *Project sync* for the *Demo project* to confirm the job is getting executed.
+
+. In *Automation Execution* click on *Templates* and edit the *Demo Job Template*. 
+
+. Click on *Instance groups* and select *executionplane* and save the job template. 
+
+. Run the job for *Demo Job Template*. 
+
+. Go to jobs *select Demo Job Template* and check the *Details* section in the job and vefiry its getting executed on the execution plane.
+
+. You can go to *Automation Execution* and then *Infrastructure* and check the *Topology View* for the current architecture of Ansible Automation Platform.

modules/chapter1/pages/section5.adoc

@@ -57,5 +57,4 @@ You need to deploy 1 execution node, 1 control node, 1 database node, and 1 Unif
 - Forks set to 5 on playbooks. This is the default. 					
 - The average event size is 1 Mb.	
 
- Note: 
- The above is true for RPM and Containerized environments.
+ Note:  The above is true for RPM and Containerized environments. The Openshift realted content will be added later.

modules/chapter1/pages/section6.adoc

@@ -1,9 +1,6 @@
 = Performance Consideration 
 
-Now from the previous information, you have got a very brief idea about the deployment and calculating the sizing requirement. Where as this is not it
-// The second statement looks incomplete.
-
-Few tips that will help you better plan the deployment for the Control and Execution plane: 
+Now from the previous information, you have got a very brief idea about the deployment and calculating the sizing requirement. Where as there are Few tips that will help you better plan the deployment for the Control and Execution plane: 
 
 The Default Parameters that do not need to be changed unless needed and you know the exact value it needs to be changed to: 
 
@@ -18,8 +15,8 @@ The Default Parameters that do not need to be changed unless needed and you know
 . Automation Controller RAM per event fork  is 10 kb. 
 . Automation Controller CPU per event fork 0.0001. 
 . Concurrent API calls per controller is 100 by default and it can reach up to 300 calls. 
-. Controlled base Job per capacity unit is 1. 
-// Controller?
+. Controller/execution base Job capacity for every job run in unit is 1. 
+
 
 The factors that will depend across different customers and environments: