diff --git a/content/os/v1.x/en/about/security/_index.md b/content/os/v1.x/en/about/security/_index.md
index fff35a2ebbe..96b8c79470d 100644
--- a/content/os/v1.x/en/about/security/_index.md
+++ b/content/os/v1.x/en/about/security/_index.md
@@ -11,7 +11,7 @@ weight: 303
Reporting process
-Please submit possible security issues by emailing security@rancher.com
+Please submit possible security issues by emailing security@rancher.com
|
Announcments
diff --git a/content/rancher/v2.x/en/installation/ha/rke-add-on/layer-4-lb/_index.md b/content/rancher/v2.x/en/installation/ha/rke-add-on/layer-4-lb/_index.md
index 8a6c5c98106..86685653fde 100644
--- a/content/rancher/v2.x/en/installation/ha/rke-add-on/layer-4-lb/_index.md
+++ b/content/rancher/v2.x/en/installation/ha/rke-add-on/layer-4-lb/_index.md
@@ -15,53 +15,22 @@ This set of instructions creates a new Kubernetes cluster that's dedicated to ru
Installation of Rancher in a high-availability configuration involves multiple procedures. Review this outline to learn about each procedure you need to complete.
-1. [Provision Linux Hosts](#1-provision-linux-hosts)
+
- Provision three Linux hosts to serve as your Kubernetes cluster.
+- [1. Provision Linux Hosts](#1-provision-linux-hosts)
+- [2. Configure Load Balancer](#2-configure-load-balancer)
+- [3. Configure DNS](#3-configure-dns)
+- [4. Download RKE](#4-download-rke)
+- [5. Download RKE Config File Template](#5-download-rke-config-file-template)
+- [6. Configure Nodes](#6-configure-nodes)
+- [7. Configure Certificates](#7-configure-certificates)
+- [8. Configure FQDN](#8-configure-fqdn)
+- [9. Configure Rancher version](#9-configure-rancher-version)
+- [10. Back Up Your RKE Config File](#10-back-up-your-rke-config-file)
+- [11. Run RKE](#11-run-rke)
+- [12. Back Up Auto-Generated Config File](#12-back-up-auto-generated-config-file)
-2. [Configure Load Balancer](#2-configure-load-balancer)
-
- Configure your load balancer to have a highly available single point of entry to your Rancher cluster.
-
-3. [Configure DNS](#3-configure-dns)
-
- Make your setup accessible using a DNS name by configuring the DNS to point to your loadbalancer.
-
-4. [Download RKE](#4-download-rke)
-
- [RKE](https://github.com/rancher/rke/releases) is a fast, versatile Kubernetes installer that you can use to install Kubernetes on your Linux hosts.
-
-5. [Download RKE Config File Template](#5-download-rke-config-file-template)
-
- RKE uses a YAML config file to install and configure your Kubernetes cluster. Download one of our RKE config file templates to get started.
-
-6. [Configure Nodes](#6-configure-nodes)
-
- Configure the **Nodes** section of the RKE config template.
-
-7. [Configure Certificates](#7-configure-certificates)
-
- Configure the **Certificates** part of the template too.
-
-8. [Configure FQDN](#8-configure-fqdn)
-
- And the **FQDN** part.
-
-9. [Configure Rancher version](#9-configure-rancher-version)
-
- Configure the **Rancher version** to use.
-
-10. [Back Up Your RKE Config File](#10-back-up-your-rke-config-file)
-
- After you've completed configuration of the RKE config file: 1. it's no longer a template since you'll be using it, and 2. you should back up the RKE config file to a safe place. You will reuse this file for upgrades later.
-
-11. [Run RKE](#11-run-rke)
-
- Run RKE to deploy Rancher to your cluster.
-
-12. [Back Up Auto-Generated Config File](#12-back-up-auto-generated-config-file)
-
- During installation, RKE generates a config file that you'll use later for upgrades. Back it up to a safe location.
+
@@ -235,8 +204,8 @@ RKE uses a `.yml` config file to install and configure your Kubernetes cluster.
- [Template for certificate signed by recognized CA
`3-node-certificate-recognizedca.yml`](https://raw.githubusercontent.com/rancher/rancher/d8ca0805a3958552e84fdf5d743859097ae81e0b/rke-templates/3-node-certificate-recognizedca.yml)
>**Want records of all transactions with the Rancher API?**
- >
- >Enable the [API Auditing]({{< baseurl >}}/rancher/v2.x/en/installation/api-auditing) feature by editing your RKE config file. For more information, see [RKE Documentation: API Auditing]({{< baseurl >}}\rke\v0.1.x\en\config-options\add-ons\api-auditing).
+ >
+ >Enable the [API Auditing]({{< baseurl >}}/rancher/v2.x/en/installation/api-auditing/) feature by editing your RKE config file. For more information, see [RKE Documentation: API Auditing]({{< baseurl >}}/rke/v0.1.x/en/config-options/add-ons/api-auditing/).
2. Rename the file to `rancher-cluster.yml`.
diff --git a/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/_index.md b/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/_index.md
index ff74135e35d..fd379c81c4b 100644
--- a/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/_index.md
+++ b/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/_index.md
@@ -55,7 +55,7 @@ The `system` project:
>**Note:** In clusters where both:
>
-> - The [Canal network plug-in]({{< baseurl >}}\rancher\v2.x\en\cluster-provisioning\rke-clusters\options\#canal) is in use.
+> - The [Canal network plug-in]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/#canal) is in use.
> - The Project Network Isolation option is enabled.
>
>The `system` project overrides the Project Network Isolation option so that it can communicate with other projects, collect logs, and check health.
diff --git a/content/rke/v0.1.x/en/config-options/add-ons/_index.md b/content/rke/v0.1.x/en/config-options/add-ons/_index.md
index c03a3c31d9b..64914d11ab4 100644
--- a/content/rke/v0.1.x/en/config-options/add-ons/_index.md
+++ b/content/rke/v0.1.x/en/config-options/add-ons/_index.md
@@ -9,7 +9,7 @@ RKE supports pluggable add-ons. Add-ons are used to deploy several cluster compo
* [Ingress controller]({{< baseurl >}}/rke/v0.1.x/en/config-options/add-ons/ingress-controllers/)
* KubeDNS
-The images used for these add-ons under the [`system_images` directive]({< baseurl >}}/rke/v0.1.x/en/config-options/system-images/). For each Kubernetes version, there are default images associated with each add-on, but these can be overridden by changing the image tag in `system_images`.
+The images used for these add-ons under the [`system_images` directive]({{< baseurl >}}/rke/v0.1.x/en/config-options/system-images/). For each Kubernetes version, there are default images associated with each add-on, but these can be overridden by changing the image tag in `system_images`.
In addition to these pluggable add-ons, you can specify an add-on that you want deployed after the cluster deployment is complete.
@@ -27,7 +27,7 @@ As of version v0.1.7, add-ons are split into two categories:
- **Critical add-ons:** If these add-ons fail to deploy for any reason, RKE will error out.
- **Non-critical add-ons:** If these add-ons fail to deploy, RKE will only log a warning and continue deploying any other add-ons.
-Currently, only the [network plug-in]({{< baseurl >}}/rke/v0.1.x/en/config-options/network-plugins/) is considered critical. KubeDNS, [ingress controllers]({{< baseurl >}}/rke/v0.1.x/en/config-options/ingress-controllers/) and [user-defined add-ons]({{< baseurl >}}/rke/v0.1.x/en/config-options/user-defined-add-ons/) are considered non-critical.
+Currently, only the [network plug-in]({{< baseurl >}}/rke/v0.1.x/en/config-options/add-ons/network-plugins/) is considered critical. KubeDNS, [ingress controllers]({{< baseurl >}}/rke/v0.1.x/en/config-options/add-ons/ingress-controllers/) and [user-defined add-ons]({{< baseurl >}}/rke/v0.1.x/en/config-options/add-ons/user-defined-add-ons/) are considered non-critical.
## Add-on deployment jobs
diff --git a/content/rke/v0.1.x/en/config-options/add-ons/ingress-controllers/_index.md b/content/rke/v0.1.x/en/config-options/add-ons/ingress-controllers/_index.md
index 0a8f6d8ca62..6865e1a535c 100644
--- a/content/rke/v0.1.x/en/config-options/add-ons/ingress-controllers/_index.md
+++ b/content/rke/v0.1.x/en/config-options/add-ons/ingress-controllers/_index.md
@@ -9,7 +9,7 @@ By default, RKE deploys the nginx ingress controller on all schedulable nodes.
RKE will deploy the ingress controller as a DaemonSet with `hostnetwork: true`, so ports `80`, and `443` will be opened on each node where the controller is deployed.
-The images used for ingress controller is under the [`system_images` directive]({< baseurl >}}/rke/v0.1.x/en/config-options/system-images/). For each Kubernetes version, there are default images associated with the ingress controller, but these can be overridden by changing the image tag in `system_images`.
+The images used for ingress controller is under the [`system_images` directive]({{< baseurl >}}/rke/v0.1.x/en/config-options/system-images/). For each Kubernetes version, there are default images associated with the ingress controller, but these can be overridden by changing the image tag in `system_images`.
## Scheduling Ingress Controllers
diff --git a/content/rke/v0.1.x/en/config-options/add-ons/network-plugins/_index.md b/content/rke/v0.1.x/en/config-options/add-ons/network-plugins/_index.md
index a450cc3b661..102f8dbd61e 100644
--- a/content/rke/v0.1.x/en/config-options/add-ons/network-plugins/_index.md
+++ b/content/rke/v0.1.x/en/config-options/add-ons/network-plugins/_index.md
@@ -18,7 +18,7 @@ network:
plugin: flannel
```
-The images used for network plug-ins are under the [`system_images` directive]({< baseurl >}}/rke/v0.1.x/en/config-options/system-images/). For each Kubernetes version, there are default images associated with each network plug-in, but these can be overridden by changing the image tag in `system_images`.
+The images used for network plug-ins are under the [`system_images` directive]({{< baseurl >}}/rke/v0.1.x/en/config-options/system-images/). For each Kubernetes version, there are default images associated with each network plug-in, but these can be overridden by changing the image tag in `system_images`.
## Network Plug-in Options
diff --git a/layouts/shortcodes/ports_aws_securitygroup_nodedriver.html b/layouts/shortcodes/ports_aws_securitygroup_nodedriver.html
index 9f45ef205ae..32536ec2ef7 100644
--- a/layouts/shortcodes/ports_aws_securitygroup_nodedriver.html
+++ b/layouts/shortcodes/ports_aws_securitygroup_nodedriver.html
@@ -1,5 +1,5 @@
Amazon EC2 security group when using Node Driver
- If you are Creating an Amazon EC2 Cluster, you can choose to let Rancher create a Security Group called rancher-nodes. The following rules are automatically added to this Security Group.
+ If you are Creating an Amazon EC2 Cluster, you can choose to let Rancher create a Security Group called rancher-nodes. The following rules are automatically added to this Security Group.
Security group: rancher-nodes
|