Add GA tag; spelling fixes

Author: 0xHiteshPatel

docs/class1/module1/lab5.rst

@@ -6,8 +6,8 @@ Lab 1.5: Building Imperative Workflows with Postman Collections
    digraph breadcrumb {
       rankdir="LR"
       ranksep=.4
-      node [fontsize=10,style="rounded,filled",shape=box,color=gray72,margin="0.05,0.05",height=0.1] 
-      fontname = "arial-bold" 
+      node [fontsize=10,style="rounded,filled",shape=box,color=gray72,margin="0.05,0.05",height=0.1]
+      fontname = "arial-bold"
       fontsize = 10
       labeljust="l"
       subgraph cluster_provider {
@@ -24,7 +24,7 @@ Lab 1.5: Building Imperative Workflows with Postman Collections
          basics -> authentication -> globalsettings -> networking -> clustering -> transactions
       }
    }
-   
+
 As you have seen in the previous labs, we can use the Collections and Folders
 features of the Postman client to group REST requests logically.  Additionally,
 as you've seen most of the examples so far have consisted of executing a
@@ -75,13 +75,13 @@ Task 1 - Open and Run a Collection
    Your Runner window should look like:
 
    |image102|
-    
-   As you can see from the screenshot or your own Collection Runner screen, we 
-   will be sending 3 requests (Steps 1-3 in Lab 1.5).  Each request has a 
+
+   As you can see from the screenshot or your own Collection Runner screen, we
+   will be sending 3 requests (Steps 1-3 in Lab 1.5).  Each request has a
    *unit test* implemented in JavaScript to ensure it's ok to continue to the
    next request when using the Collection Runner. The Runner will step through
    each request unless one of the tests fails.
-    
+
 #. Click the :guilabel:`Run Lab 1.5 - Buil...` button
 
 #. The results window will now populate.  You will see each request in the
@@ -98,8 +98,8 @@ Task 1 - Open and Run a Collection
 
    |image104|
 
-.. NOTE:: It is normal for the values of Software Version, CPU Count and Base 
-   MAC Address to be different from the screenshot(s).  
+.. NOTE:: It is normal for the values of Software Version, CPU Count and Base
+   MAC Address to be different from the screenshot(s).
 
 In this lab, we demonstrated running a simple Imperative Workflow using the
 Postman Collection Runner.  In subsequent labs, we will expand on this simple

docs/class1/module2/lab3.rst

@@ -75,7 +75,7 @@ Perform the following steps to complete this task:
       order of operations and configuration of specific objects.  By doing this,
       we have drastically reduced the amount of **Domain Specific Knowledge**
       required to interact with the device.  In the next module, we will combine
-      this concept with **Abstraction** to further simplify the interface the 
+      this concept with **Abstraction** to further simplify the interface the
       service consumer has to interact with.
 
 #. Now that the service has been deployed, let's review the BIG-IP configuration.
@@ -151,9 +151,9 @@ Perform the following steps to complete this task:
 
    |image2_19|
 
-#. Similar to modification process, the deletion of a service is performed on 
-   the **Resource** URL. When we created the service, we defined a Declarative 
-   state to the iApp template which subsequently created the configuration and 
+#. Similar to modification process, the deletion of a service is performed on
+   the **Resource** URL. When we created the service, we defined a Declarative
+   state to the iApp template which subsequently created the configuration and
    all of its associated objects.  With a ``DELETE`` request, BIG-IP will process
    the removal of all objects linked to the ASO in a recursive manner. This is
    crucial to Application Lifecycle Management as it provides a mechanism to
@@ -278,8 +278,8 @@ Perform the following steps to complete this task:
    .. IMPORTANT:: RFC2616 (HTTP/1.1) allows for a TCP session to stay open.
       Had we not included "noserver Cache-Control no-cache *Connection Close*"
       in the iRule the following would have happened:
-   
-      When you would have refreshed the page, the maintenance page would still 
+
+      When you would have refreshed the page, the maintenance page would still
       appear because of two reasons:
 
       #. Chrome keeps HTTP connections open in the background to improve network
@@ -291,8 +291,8 @@ Perform the following steps to complete this task:
 
       As a result, because Chrome has not closed the actual TCP connection,
       BIG-IP still processes traffic with the configuration that was present
-      when the connection was originally created.  That *stale* connection 
-      was still using the verison of the configuration with the iRule attached
+      when the connection was originally created.  That *stale* connection
+      was still using the version of the configuration with the iRule attached
       to the Virtual Service resulting in the maintenance page being shown.
 
    |image2_30|

docs/class1/module2/module2.rst

@@ -6,8 +6,8 @@ Module 2: Abstracting Services using iApp Templates
    digraph breadcrumb {
       rankdir="LR"
       ranksep=.4
-      node [fontsize=10,style="rounded,filled",shape=box,color=gray72,margin="0.05,0.05",height=0.1] 
-      fontname = "arial-bold" 
+      node [fontsize=10,style="rounded,filled",shape=box,color=gray72,margin="0.05,0.05",height=0.1]
+      fontname = "arial-bold"
       fontsize = 10
       labeljust="l"
       subgraph cluster_provider {
@@ -40,7 +40,7 @@ through the use of a custom iApp Template.
 
 iApps are commonly thought of as a Wizard style deployment helper, but they are
 actually a Declarative Interface.  When iApp Templates are created they can be
-written to accodomodate API centric use cases.
+written to accomodate API centric use cases.
 
 When an iApp deploys, a **single** call - declaring the desired deployment -
 is processed on the BIG-IP with the correct order of operations.
@@ -66,15 +66,15 @@ at:
 
 .. NOTE:: This module requires the underlying network configuration that was
    completed in Module 1.  Additionally, **BIG-IP A** must be the **Active**
-   node in the cluster.  When viewing the BIG-IP A GUI it should say 
+   node in the cluster.  When viewing the BIG-IP A GUI it should say
    ``ONLINE (ACTIVE)`` in the upper left corner of the interface.
 
 .. NOTE:: This module deploys the configuration to BIG-IP A. iApp deployments
    leverage the underlying config-sync mechanisms in the cluster.  Once deployed
    on BIG-IP A, the configuration will be automatically synced to BIG-IP B.
-   
+
    You can learn more about clustering features in this video:
-   
+
    https://www.youtube.com/watch?v=RAQ1qaYnjZo
 
 .. toctree::

docs/conf.py

@@ -67,11 +67,15 @@
     'sphinx.ext.ifconfig',
     'sphinx.ext.extlinks',
     'sphinx.ext.graphviz',
-    'sphinxcontrib.spelling'
+    'sphinxcontrib.spelling',
+    'sphinxcontrib.googleanalytics'
 ]
 
 spelling_word_list_filename = "../wordlist"
 
+googleanalytics_id = 'UA-85156643-6'
+googleanalytics_enabled = True
+
 # Add any paths that contain templates here, relative to this directory.
 templates_path = ['_templates']
 

wordlist

@@ -124,10 +124,12 @@ loadBalancingMode
 localhost
 ltm
 mgmt
+noserver
 netops
 newman
 noVNC
 offline
+ok
 onboarding
 plaintext
 pre