edits

Author: travisamartin

content/nginx/deployment-guides/amazon-web-services/route-53-global-server-load-balancing.md

@@ -186,7 +186,7 @@ We create health checks both for each NGINX Plus load balancer individually and
 
    <img src="https://cdn-1.wp.nginx.com/wp-content/uploads/2016/10/aws-route53-get-notified-health-check.png" alt="Screenshot of Route 53 configuration screen for enabling notifications of failed health checks, during configuration of Route 53 global load balancing (GLB) with NGINX Plus" style="border:2px solid #666666; padding:2px; margin:2px;" />
 
-4. Repeat Steps 2 and 3 for your other NGINX Plus load balancers (in this guide, {{<nb>}}**US West LB 2**,{{</nb>}} {{<nb>}}**US East LB 1**,{{</nb>}} and {{<nb>}}**US East LB 2**){{</nb>}}.
+4. Repeat Steps 2 and 3 for your other NGINX Plus load balancers (in this guide, {{<nb>}}**US West LB 2**{{</nb>}}, {{<nb>}}**US East LB 1**{{</nb>}}, and {{<nb>}}**US East LB 2**){{</nb>}}.
 
 5. Proceed to the next section to configure health checks for the load balancer pairs.
 
@@ -282,9 +282,9 @@ These instructions assume that you have configured NGINX Plus on two EC2 instan
    nginx -s reload
    ```
 
-5. Repeat Steps 1 through 4 for the other three load balancers {{<nb>}}(**US West LB 2**,{{</nb>}} {{<nb>}}**US East LB 1**,{{</nb>}} and {{<nb>}}**US East LB2**){{</nb>}}.
+5. Repeat Steps 1 through 4 for the other three load balancers {{<nb>}}(**US West LB 2**{{</nb>}}, {{<nb>}}**US East LB 1**{{</nb>}}, and {{<nb>}}**US East LB2**){{</nb>}}.
 
-   In Step 3, change the filename as appropriate {{<nb>}}(**west-lb2.conf**,{{</nb>}} {{<nb>}}**east-lb1.conf**,{{</nb>}} and {{<nb>}}**east-lb2.conf**){{</nb>}}. In the {{<nb>}}**east-lb1.conf**{{</nb>}} and {{<nb>}}**east-lb2.conf**{{</nb>}} files, the `server` directives specify the public DNS names of Backup 3 and Backup 4.
+   In Step 3, change the filename as appropriate {{<nb>}}(**west-lb2.conf**{{</nb>}}, {{<nb>}}**east-lb1.conf**{{</nb>}}, and {{<nb>}}**east-lb2.conf**){{</nb>}}. In the {{<nb>}}**east-lb1.conf**{{</nb>}} and {{<nb>}}**east-lb2.conf**{{</nb>}} files, the `server` directives specify the public DNS names of Backup 3 and Backup 4.
 
 <span id="appendix"></span>
 ## Appendix
@@ -366,7 +366,7 @@ After you complete the instructions on all instances, the list for a region (her
 <span id="configure-backend-servers"></span>
 ### Configuring NGINX Open Source on the Backend Servers
 
-Perform these steps on all four backend servers: {{<nb>}}**Backend 1**,{{</nb>}} {{<nb>}}**Backend 2**,{{</nb>}} {{<nb>}}**Backend 3**,{{</nb>}} and {{<nb>}}**Backend 4**{{</nb>}}. In Step 3, substitute the appropriate name for `Backend X` in the **index.html** file.
+Perform these steps on all four backend servers: {{<nb>}}**Backend 1**{{</nb>}}, {{<nb>}}**Backend 2**{{</nb>}}, {{<nb>}}**Backend 3**{{</nb>}}, and {{<nb>}}**Backend 4**{{</nb>}}. In Step 3, substitute the appropriate name for `Backend X` in the **index.html** file.
 
 **Note:** Some commands require `root` privilege. If appropriate for your environment, prefix commands with the `sudo` command.
 
@@ -421,7 +421,7 @@ Perform these steps on all four backend servers: {{<nb>}}**Backend 1**,{{</nb>}}
 <span id="configure-load-balancers"></span>
 ### Configuring NGINX Plus on the Load Balancers
 
-Perform these steps on all four backend servers: {{<nb>}}**US West LB 1**,{{</nb>}} {{<nb>}}**US West LB 2**,{{</nb>}} {{<nb>}}**US East LB 1**,{{</nb>}} and {{<nb>}}**US West LB 2**{{</nb>}}.
+Perform these steps on all four backend servers: {{<nb>}}**US West LB 1**{{</nb>}}, {{<nb>}}**US West LB 2**{{</nb>}}, {{<nb>}}**US East LB 1**{{</nb>}}, and {{<nb>}}**US West LB 2**{{</nb>}}.
 
 **Note:** Some commands require `root` privilege. If appropriate for your environment, prefix commands with the `sudo` command.
 

content/nginx/deployment-guides/google-cloud-platform/high-availability-all-active.md

@@ -205,7 +205,7 @@ Create three source VM instances based on a GCE VM image. We're basing our insta
 
 Install and configure PHP and FastCGI on the instances.
 
-<span style="text-decoration: underline; white-space: nowrap;">Repeat these instructions</span> for all three source instances {{<nb>}}(**nginx-plus-app-1**,{{</nb>}} {{<nb>}}**nginx-plus-app-2**,{{</nb>}} and {{<nb>}}**nginx-plus-lb**){{</nb>}}.
+<span style="text-decoration: underline; white-space: nowrap;">Repeat these instructions</span> for all three source instances {{<nb>}}(**nginx-plus-app-1**{{</nb>}}, {{<nb>}}**nginx-plus-app-2**{{</nb>}}, and {{<nb>}}**nginx-plus-lb**){{</nb>}}.
 
 **Note:** Some commands require `root` privilege. If appropriate for your environment, prefix commands with the `sudo` command.
 
@@ -253,7 +253,7 @@ Now install NGINX Plus and download files that are specific to the all‑active
 
 Both the configuration and content files are available at the [NGINX GitHub repository](https://github.com/nginxinc/NGINX-Demos/tree/master/gce-nginx-plus-deployment-guide-files).
 
-<span style="text-decoration: underline; white-space: nowrap;">Repeat these instructions</span> for all three source instances {{<nb>}}(**nginx-plus-app-1**,{{</nb>}} {{<nb>}}**nginx-plus-app-2**,{{</nb>}} and {{<nb>}}**nginx-plus-lb**){{</nb>}}.
+<span style="text-decoration: underline; white-space: nowrap;">Repeat these instructions</span> for all three source instances {{<nb>}}(**nginx-plus-app-1**{{</nb>}}, {{<nb>}}**nginx-plus-app-2**{{</nb>}}, and {{<nb>}}**nginx-plus-lb**){{</nb>}}.
 
 **Note:** Some commands require `root` privilege. If appropriate for your environment, prefix commands with the `sudo` command.
 
@@ -265,7 +265,7 @@ Both the configuration and content files are available at the [NGINX GitHub repo
 
 4. Copy the right configuration file from the **etc\_nginx\_conf.d** subdirectory of the cloned repository to **/etc/nginx/conf.d**:
 
-   - On <span style="text-decoration: underline;">both</span> {{<nb>}}**nginx-plus-app-1**{{</nb>}} and {{<nb>}}**nginx-plus-app-2**,{{</nb>}} copy {{<nb>}}**gce-all-active-app.conf**{{</nb>}}.
+   - On <span style="text-decoration: underline;">both</span> {{<nb>}}**nginx-plus-app-1**{{</nb>}} and {{<nb>}}**nginx-plus-app-2**{{</nb>}}, copy {{<nb>}}**gce-all-active-app.conf**{{</nb>}}.
 
       You can also run the following commands to download the configuration file directly from the GitHub repository:
 
@@ -281,7 +281,7 @@ Both the configuration and content files are available at the [NGINX GitHub repo
       wget https://github.com/nginxinc/NGINX-Demos/blob/master/gce-nginx-plus-deployment-guide-files/etc_nginx_conf.d/gce-all-active-app.conf
       ```
 
-   - On {{<nb>}}**nginx-plus-lb**,{{</nb>}} copy {{<nb>}}**gce-all-active-lb.conf**{{</nb>}}.
+   - On {{<nb>}}**nginx-plus-lb**{{</nb>}}, copy {{<nb>}}**gce-all-active-lb.conf**{{</nb>}}.
 
      You can also run the following commands to download the configuration file directly from the GitHub repository:
 
@@ -297,7 +297,7 @@ Both the configuration and content files are available at the [NGINX GitHub repo
       wget https://github.com/nginxinc/NGINX-Demos/blob/master/gce-nginx-plus-deployment-guide-files/etc_nginx_conf.d/gce-all-active-lb.conf
       ```
 
-5. On the LB instance {{<nb>}}(**nginx-plus-lb**),{{</nb>}} use a text editor to open {{<nb>}}**gce-all-active-lb.conf**{{</nb>}}. Change the `server` directives in the `upstream` block to reference the internal IP addresses of the {{<nb>}}**nginx-plus-app-1**{{</nb>}} and {{<nb>}}**nginx-plus-app-2**{{</nb>}} instances (substitute the address for the expression in angle brackets). You do not need to modify the two application instances.
+5. On the LB instance {{<nb>}}(**nginx-plus-lb**){{</nb>}}, use a text editor to open {{<nb>}}**gce-all-active-lb.conf**{{</nb>}}. Change the `server` directives in the `upstream` block to reference the internal IP addresses of the {{<nb>}}**nginx-plus-app-1**{{</nb>}} and {{<nb>}}**nginx-plus-app-2**{{</nb>}} instances (substitute the address for the expression in angle brackets). You do not need to modify the two application instances.
 
    You can look up internal IP addresses in the {{<nb>}}**Internal IP**{{</nb>}} column of the table on the {{<nb>}}**Compute Engine > VM instances**{{</nb>}} summary page.
 
@@ -400,7 +400,7 @@ Create three source instances based on a prebuilt NGINX Plus image running on <
 
 9. Modify or verify the indicated editable fields (non‑editable fields are not listed):
 
-   - **Tags** – If a default tag appears (for example, {{<nb>}}**nginx-plus-app-1-tcp-80**),{{</nb>}} click the **X** after its name to remove it. Then, type in {{<nb>}}**nginx-plus-http-fw-rule**{{</nb>}}.
+   - **Tags** – If a default tag appears (for example, {{<nb>}}**nginx-plus-app-1-tcp-80**){{</nb>}}, click the **X** after its name to remove it. Then, type in {{<nb>}}**nginx-plus-http-fw-rule**{{</nb>}}.
    - {{<nb>}}**External IP**{{</nb>}} – **Ephemeral** (the default)
    - {{<nb>}}**Boot disk and local disks**{{</nb>}} – Uncheck the checkbox labeled **Delete boot disk when instance is deleted**.
    - {{<nb>}}**Additional disks**{{</nb>}} – No changes
@@ -435,7 +435,7 @@ Create the second application instance by cloning the first one.
 
    - **Name** – {{<nb>}}**nginx-plus-app-2-vm**{{</nb>}}. Here we're adding the {{<nb>}}**-vm**{{</nb>}} suffix to make the name consistent with the first instance; GCE does not add it automatically when you clone an instance.
    - **Zone** – The GCP zone that makes sense for your location. We're using {{<nb>}}**us-west1-a**{{</nb>}}.
-   - {{<nb>}}**Machine type**{{</nb>}} – The appropriate size for the level of traffic you anticipate. We're selecting {{<nb>}}**f1-micro**,{{</nb>}} which is ideal for testing purposes.
+   - {{<nb>}}**Machine type**{{</nb>}} – The appropriate size for the level of traffic you anticipate. We're selecting {{<nb>}}**f1-micro**{{</nb>}}, which is ideal for testing purposes.
    - {{<nb>}}**Boot disk type**{{</nb>}} – {{<nb>}}**New 10 GB standard persistent disk**{{</nb>}} (the value inherited from {{<nb>}}**nginx-plus-app-1-vm**){{</nb>}}
    - {{<nb>}}**Identity and API access**{{</nb>}} – Set the {{<nb>}}**Access scopes**{{</nb>}} radio button to {{<nb>}}**Allow default access**{{</nb>}} and accept the default values in all other fields. If you want more granular control over access than is provided by these settings, modify the fields in this section as appropriate.
    - **Firewall** – Verify that neither check box is checked (the default).
@@ -461,7 +461,7 @@ Repeat Steps 2 through 7 of <a href="#source-prebuilt-app-2">Creating the Seco
 
 Install and configure PHP and FastCGI on the instances.
 
-<span style="text-decoration: underline; white-space: nowrap;">Repeat these instructions</span> for all three source instances {{<nb>}}(**nginx-plus-app-1-vm**,{{</nb>}} {{<nb>}}**nginx-plus-app-2-vm**,{{</nb>}} and {{<nb>}}**nginx-plus-lb-vm**){{</nb>}}.
+<span style="text-decoration: underline; white-space: nowrap;">Repeat these instructions</span> for all three source instances {{<nb>}}(**nginx-plus-app-1-vm**{{</nb>}}, {{<nb>}}**nginx-plus-app-2-vm**{{</nb>}}, and {{<nb>}}**nginx-plus-lb-vm**){{</nb>}}.
 
 **Note:** Some commands require `root` privilege. If appropriate for your environment, prefix commands with the `sudo` command.
 
@@ -511,7 +511,7 @@ Now download files that are specific to the all‑active deployment:
 
 Both the configuration and content files are available at the [NGINX GitHub repository](https://github.com/nginxinc/NGINX-Demos/tree/master/gce-nginx-plus-deployment-guide-files).
 
-<span style="text-decoration: underline; white-space: nowrap;">Repeat these instructions</span> for all three source instances {{<nb>}}(**nginx-plus-app-1-vm**,{{</nb>}} {{<nb>}}**nginx-plus-app-2-vm**,{{</nb>}} and {{<nb>}}**nginx-plus-lb-vm**){{</nb>}}.
+<span style="text-decoration: underline; white-space: nowrap;">Repeat these instructions</span> for all three source instances {{<nb>}}(**nginx-plus-app-1-vm**{{</nb>}}, {{<nb>}}**nginx-plus-app-2-vm**{{</nb>}}, and {{<nb>}}**nginx-plus-lb-vm**){{</nb>}}.
 
 **Note:** Some commands require `root` privilege. If appropriate for your environment, prefix commands with the `sudo` command.
 
@@ -522,7 +522,7 @@ Both the configuration and content files are available at the [NGINX GitHub repo
 
 3. Copy the right configuration file from the **etc\_nginx\_conf.d** subdirectory of the cloned repository to **/etc/nginx/conf.d**:
 
-   - On <span style="text-decoration: underline;">both</span> {{<nb>}}**nginx-plus-app-1-vm**{{</nb>}} and {{<nb>}}**nginx-plus-app-2-vm**,{{</nb>}} copy {{<nb>}}**gce-all-active-app.conf**{{</nb>}}.
+   - On <span style="text-decoration: underline;">both</span> {{<nb>}}**nginx-plus-app-1-vm**{{</nb>}} and {{<nb>}}**nginx-plus-app-2-vm**{{</nb>}}, copy {{<nb>}}**gce-all-active-app.conf**{{</nb>}}.
 
      You can also run these commands to download the configuration file from GitHub:
 
@@ -538,7 +538,7 @@ Both the configuration and content files are available at the [NGINX GitHub repo
       wget https://github.com/nginxinc/NGINX-Demos/blob/master/gce-nginx-plus-deployment-guide-files/etc_nginx_conf.d/gce-all-active-app.conf
       ```
 
-   - On {{<nb>}}**nginx-plus-lb-vm**,{{</nb>}} copy {{<nb>}}**gce-all-active-lb.conf**{{</nb>}}.
+   - On {{<nb>}}**nginx-plus-lb-vm**{{</nb>}}, copy {{<nb>}}**gce-all-active-lb.conf**{{</nb>}}.
 
       You can also run the following commands to download the configuration file directly from the GitHub repository:
 
@@ -554,7 +554,7 @@ Both the configuration and content files are available at the [NGINX GitHub repo
       wget https://github.com/nginxinc/NGINX-Demos/blob/master/gce-nginx-plus-deployment-guide-files/etc_nginx_conf.d/gce-all-active-lb.conf
       ```
 
-4. On the LB instance {{<nb>}}(**nginx-plus-lb-vm**),{{</nb>}} use a text editor to open {{<nb>}}**gce-all-active-lb.conf**{{</nb>}}. Change the `server` directives in the `upstream` block to reference the internal IP addresses of the {{<nb>}}**nginx-plus-app-1-vm**{{</nb>}} and {{<nb>}}**nginx-plus-app-2-vm**{{</nb>}} instances. (No action is required on the two application instances themselves.)
+4. On the LB instance {{<nb>}}(**nginx-plus-lb-vm**){{</nb>}}, use a text editor to open {{<nb>}}**gce-all-active-lb.conf**{{</nb>}}. Change the `server` directives in the `upstream` block to reference the internal IP addresses of the {{<nb>}}**nginx-plus-app-1-vm**{{</nb>}} and {{<nb>}}**nginx-plus-app-2-vm**{{</nb>}} instances. (No action is required on the two application instances themselves.)
 
    You can look up internal IP addresses in the {{<nb>}}**Internal IP**{{</nb>}} column of the table on the {{<nb>}}**Compute Engine > VM instances**{{</nb>}} summary page.
 
@@ -623,8 +623,8 @@ Create _gold images_, which are base images that GCE clones automatically when i
 
 3. In the table, select all three instances:
 
-   - If you created source instances from [VM (Ubuntu) images](#source-vm): {{<nb>}}**nginx-plus-app-1**,{{</nb>}} {{<nb>}}**nginx-plus-app-2**,{{</nb>}} and {{<nb>}}**nginx-plus-lb**{{</nb>}}
-   - If you created source instances from [prebuilt NGINX Plus images](#source-prebuilt): {{<nb>}}**nginx-plus-app-1-vm**,{{</nb>}} {{<nb>}}**nginx-plus-app-2-vm**,{{</nb>}} and {{<nb>}}**nginx-plus-lb-vm**{{</nb>}}
+   - If you created source instances from [VM (Ubuntu) images](#source-vm): {{<nb>}}**nginx-plus-app-1**{{</nb>}}, {{<nb>}}**nginx-plus-app-2**{{</nb>}}, and {{<nb>}}**nginx-plus-lb**{{</nb>}}
+   - If you created source instances from [prebuilt NGINX Plus images](#source-prebuilt): {{<nb>}}**nginx-plus-app-1-vm**{{</nb>}}, {{<nb>}}**nginx-plus-app-2-vm**{{</nb>}}, and {{<nb>}}**nginx-plus-lb-vm**{{</nb>}}
 
 4. Click <span style="color:#3366cc;">STOP</span> in the top toolbar to stop the instances.
 
@@ -654,21 +654,21 @@ Create _gold images_, which are base images that GCE clones automatically when i
    - **Description** – **NGINX Plus Application 1 Gold Image**
    - **Encryption** – {{<nb>}}**Automatic (recommended)**{{</nb>}} (the default)
    - **Source** – **Disk** (the default)
-   - {{<nb>}}**Source disk**{{</nb>}} – {{<nb>}}**nginx-plus-app-1**{{</nb>}} or {{<nb>}}**nginx-plus-app-1-vm**,{{</nb>}} depending on the method you used to create source instances (select the source instance from the drop‑down menu)
+   - {{<nb>}}**Source disk**{{</nb>}} – {{<nb>}}**nginx-plus-app-1**{{</nb>}} or {{<nb>}}**nginx-plus-app-1-vm**{{</nb>}}, depending on the method you used to create source instances (select the source instance from the drop‑down menu)
 
 9. Click the <span style="background-color:#3366cc; color:white;"> Create </span> button.
 
 10. Repeat Steps 7 through 9 to create a second image with the following values (retain the default values in all other fields):
 
     - **Name** – {{<nb>}}**nginx-plus-app-2-image**{{</nb>}}
     - **Description** – **NGINX {{<nb>}}Plus Application 2 Gold Image**{{</nb>}}
-    - {{<nb>}}**Source disk**{{</nb>}} – {{<nb>}}**nginx-plus-app-2**{{</nb>}} or {{<nb>}}**nginx-plus-app-2-vm**,{{</nb>}} depending on the method you used to create source instances (select the source instance from the drop‑down menu)
+    - {{<nb>}}**Source disk**{{</nb>}} – {{<nb>}}**nginx-plus-app-2**{{</nb>}} or {{<nb>}}**nginx-plus-app-2-vm**{{</nb>}}, depending on the method you used to create source instances (select the source instance from the drop‑down menu)
 
 11. Repeat Steps 7 through 9 to create a third image with the following values (retain the default values in all other fields):
 
     - **Name** – {{<nb>}}**nginx-plus-lb-image**{{</nb>}}
     - **Description** – **NGINX Plus LB Gold Image**
-    - {{<nb>}}**Source disk**{{</nb>}} – {{<nb>}}**nginx-plus-lb**{{</nb>}} or {{<nb>}}**nginx-plus-lb-vm**,{{</nb>}} depending on the method you used to create source instances (select the source instance from the drop‑down menu)
+    - {{<nb>}}**Source disk**{{</nb>}} – {{<nb>}}**nginx-plus-lb**{{</nb>}} or {{<nb>}}**nginx-plus-lb-vm**{{</nb>}}, depending on the method you used to create source instances (select the source instance from the drop‑down menu)
 
 12. Verify that the three images appear at the top of the table on the {{<nb>}}**Compute Engine > Images**{{</nb>}} tab.
 

content/nginx/deployment-guides/load-balance-third-party/apache-tomcat.md

@@ -171,7 +171,7 @@ http {
 }
 ```
 
-You can also use wildcard notation to reference all files that pertain to a certain function or traffic type in the appropriate context block. For example, if you name all HTTP configuration files {{<nb>}}**_function_-http.conf**,{{</nb>}} this is an appropriate `include` directive:
+You can also use wildcard notation to reference all files that pertain to a certain function or traffic type in the appropriate context block. For example, if you name all HTTP configuration files {{<nb>}}**_function_-http.conf**{{</nb>}}, this is an appropriate `include` directive:
 
 ```nginx
 http {
@@ -294,7 +294,7 @@ To configure load balancing, first create a named _upstream group_, which lists
 
 2. In the `server` block for HTTPS traffic that we created in [Configuring Virtual Servers for HTTP and HTTPS Traffic](#virtual-servers), include two `location` blocks:
 
-   - The first one matches HTTPS requests in which the path starts with {{<nb>}}**/tomcat-app/**,{{</nb>}} and proxies them to the **tomcat** upstream group we created in the previous step.
+   - The first one matches HTTPS requests in which the path starts with {{<nb>}}**/tomcat-app/**{{</nb>}}, and proxies them to the **tomcat** upstream group we created in the previous step.
 
    - The second one funnels all traffic to the first `location` block, by doing a temporary redirect of all requests for **"http://example.com/"**.
 
@@ -409,7 +409,7 @@ To enable basic caching in <span style="white-space: nowrap;">NGINX Open Source<
 
    Directive documentation: [proxy_cache_path](https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cache_path)
 
-2. In the `location` block that matches HTTPS requests in which the path starts with {{<nb>}}**/tomcat-app/**,{{</nb>}} include the `proxy_cache` directive to reference the cache created in the previous step.
+2. In the `location` block that matches HTTPS requests in which the path starts with {{<nb>}}**/tomcat-app/**{{</nb>}}, include the `proxy_cache` directive to reference the cache created in the previous step.
 
    ```nginx
    # In the 'server' block for HTTPS traffic