A few more fixes.

content/blog/2018/soft-multitenancy/index.md

@@ -328,7 +328,7 @@ address the use cases.
 Current Istio capabilities are poorly suited to support the first model as it lacks
 sufficient RBAC capabilities to support cluster versus tenant operations. Additionally,
 having multiple tenants under one mesh is too insecure with the current mesh model and the
-way Istio drives configuration to the envoy proxies.
+way Istio drives configuration to the Envoy proxies.
 
 Regarding the second option, the current Istio paradigm assumes a single mesh per Istio control
 plane. The needed changes to support this model are substantial. They would require

content/blog/2019/egress-performance/index.md

@@ -27,7 +27,7 @@ Several cases for accessing the external database from the mesh were tested and
 
 ### Case 1:  Bypassing the sidecar
 
-In this case, the sidecar does not intercept the communication between the application and the external DB. This is accomplished by setting the init container argument -x with the CIDR of the MongoDB, which makes the sidecar ignore messages to/from this `ip` address. For example:
+In this case, the sidecar does not intercept the communication between the application and the external DB. This is accomplished by setting the init container argument -x with the CIDR of the MongoDB, which makes the sidecar ignore messages to/from this IP address. For example:
 
         - -x
         - "169.47.232.211/32"

content/docs/setup/kubernetes/multicluster-install/vpn/index.md

@@ -422,7 +422,7 @@ endpoints in the remote cluster, Kubernetes adds DNS entries to the `kube-dns`
 configuration object.
 
 This allows the `kube-dns` configuration object in the remote clusters to
-resolve the Istio service names for all envoy sidecars in those remote
+resolve the Istio service names for all Envoy sidecars in those remote
 clusters. Since Kubernetes pods don't have stable IPs, restart of any Istio
 service pod in the control plane cluster causes its endpoint to change.
 Therefore, any connection made from remote clusters to that endpoint are

content/help/ops/misc/index.md

@@ -87,7 +87,7 @@ An [issue](https://github.com/kubernetes/kubeadm/issues/666) was filed with Kube
 
 ## What Envoy version is Istio using?
 
-To find out the envoy version used in deployment, you can `exec` into the container and query the `server_info` endpoint:
+To find out the Envoy version used in deployment, you can `exec` into the container and query the `server_info` endpoint:
 
 {{< text bash >}}
 $ kubectl exec -it PODNAME -c istio-proxy -n NAMESPACE /bin/bash

src/sass/misc/_primary.scss

@@ -1,6 +1,5 @@
 .sidebar-container {
     grid-column: sidebar;
-    max-width: 25rem;
 
     @media print {
         display: none;
@@ -13,7 +12,6 @@
 
 .toc-container {
     grid-column: toc;
-    max-width: 25rem;
     display: none;
 }
 
@@ -37,10 +35,10 @@
             display: block;
         }
     }
-}
 
-.primary.notoc {
-    @media screen AND (min-width: $bp-xl) {
-        grid-template-columns: [sidebar] 16% [article] calc(84% - 1rem);
+    &.notoc {
+        @media screen AND (min-width: $bp-xl) {
+            grid-template-columns: [sidebar] 16% [article] calc(84% - 1rem);
+        }
     }
 }