Merge pull request #1029 from neiljerram/note-regularization

Regularize our indented NOTE box format

Author: Neil Jerram

master/getting-started/docker/tutorials/security-using-calico-profiles.md

@@ -37,7 +37,9 @@ To create the networks, run the following commands on one of the hosts:
     docker network create --driver calico --ipam-driver calico-ipam net2
     docker network create --driver calico --ipam-driver calico-ipam net3
 
->Note: To allocate from a specific Calico IP Pool, the `--subnet a.b.c.d/xx` command can be passed to `docker network create`. For more details see below.
+> **NOTE**
+>
+> To allocate from a specific Calico IP Pool, the `--subnet a.b.c.d/xx` command can be passed to `docker network create`. For more details see below.
 
 ## 2. Create the workloads in the networks
 

master/getting-started/kubernetes/installation/hosted/kubernetes-datastore/index.md

@@ -26,7 +26,9 @@ You must have a cluster which meets the following requirements:
 - Your Kubernetes controller manager is configured to allocate pod CIDRs (i.e. by passing `--allocate-node-cidrs=true` to the controller manager)
 - Your Kubernetes controller manager has been provided a cluster-cidr (i.e. by passing `--cluster-cidr=192.168.0.0/16`, which the manifest expects by default).
 
-> Note:  If you are upgrading from Calico v2.1, the cluster-cidr selected for your controller manager should remain
+> **NOTE**
+>
+> If you are upgrading from Calico v2.1, the cluster-cidr selected for your controller manager should remain
 > unchanged from the v2.1 install (the v2.1 manifests default to `10.244.0.0/16`).
 
 ## Installation
@@ -39,7 +41,9 @@ This document describes three installation options for Calico using Kubernetes A
 
 Ensure you have a cluster which meets the above requirements.  There may be additional requirements based on the installation option you choose.
 
-> Note:  There is currently no upgrade path to switch between different installation options.  Therefore,
+> **NOTE**
+>
+> There is currently no upgrade path to switch between different installation options.  Therefore,
 > if you are upgrading from Calico v2.1, use the [Calico policy-only with user-supplied networking](#2-calico-policy-only-with-user-supplied-networking) installation instructions
 > to upgrade Calico policy-only which leaves the networking solution unchanged.
 
@@ -50,7 +54,9 @@ RBAC roles to allow API access to Calico.
 
 Apply the following manifest to create these necessary RBAC roles and bindings.
 
-> Note: The following RBAC policy is compatible with the Kubernetes v1.7+ manifests only.
+> **NOTE**
+>
+> The following RBAC policy is compatible with the Kubernetes v1.7+ manifests only.
 
 ```
 kubectl apply -f {{site.url}}/{{page.version}}/getting-started/kubernetes/installation/hosted/rbac-kdd.yaml
@@ -66,7 +72,9 @@ networking with a full node-to-node mesh and/or explicit configuration of peers.
 To install Calico with Calico networking, run one of the commands below based on your Kubernetes version.
 This will install Calico and will initially create a full node-to-node mesh.
 
-> Note: Calico `v2.5.0` or higher with Kubernetes backend requires Kubernetes `v1.7.0` or higher.
+> **NOTE**
+>
+> Calico `v2.5.0` or higher with Kubernetes backend requires Kubernetes `v1.7.0` or higher.
 
 ```
 kubectl apply -f {{site.url}}/{{page.version}}/getting-started/kubernetes/installation/hosted/kubernetes-datastore/calico-networking/1.7/calico.yaml
@@ -99,7 +107,9 @@ CIDR allocations, either through static routes, a Kubernetes cloud-provider inte
 
 To install Calico in policy-only mode, run one of the following commands based on your Kubernetes version:
 
-> Note: Calico `v2.5.0` or higher with Kubernetes backend requires Kubernetes `v1.7.0` or higher.
+> **NOTE**
+>
+> Calico `v2.5.0` or higher with Kubernetes backend requires Kubernetes `v1.7.0` or higher.
 
 ```
 kubectl apply -f {{site.url}}/{{page.version}}/getting-started/kubernetes/installation/hosted/kubernetes-datastore/policy-only/1.7/calico.yaml

master/getting-started/kubernetes/installation/integration.md

@@ -20,7 +20,7 @@ installation method.
   - Calico can share the etcd cluster used by Kubernetes, but in some cases it's recommended that a separate cluster is set up.
     A number of production users do share the etcd cluster between the two, but separating them gives better performance at high scale.
 
-> **NOTE:**
+> **NOTE**
 >
 > Calico can also be installed [without a dependency on etcd](hosted/kubernetes-datastore/), but that is not covered in this document.
 
@@ -104,7 +104,7 @@ WantedBy=multi-user.target
 ```
 > Replace `<ETCD_IP>:<ETCD_PORT>` with your etcd configuration.
 
-> **NOTE:**
+> **NOTE**
 >
 > To ensure reasonable dataplane programming latency on a system under load,
 `calico/node` requires a CPU reservation of at least 0.25 cores with additional

master/getting-started/kubernetes/installation/vagrant/index.md

@@ -24,7 +24,9 @@ Run
 
     vagrant up
 
-> *Note*: This will deploy a Kubernetes master and two Kubernetes nodes.  To run more nodes, modify the value `num_instances` in the Vagrantfile before running `vagrant up`.
+> **NOTE**
+>
+> This will deploy a Kubernetes master and two Kubernetes nodes.  To run more nodes, modify the value `num_instances` in the Vagrantfile before running `vagrant up`.
 
 To connect to your servers
 

master/getting-started/kubernetes/tutorials/advanced-policy.md

@@ -55,7 +55,7 @@ kubectl expose --namespace=advanced-policy-demo deployment nginx --port=80
 
 #### Check using calicoctl
 
-  > **Note:**
+  > **NOTE**
   >
   > This requires the [calicoctl tool to be configured]({{site.baseurl}}/{{page.version}}/reference/calicoctl/setup/etcdv2).
   > For example: `export ETCD_ENDPOINTS=http://10.96.232.136:6666`
@@ -70,7 +70,7 @@ $ calicoctl get profile -o wide
 NAME                          TAGS
 k8s_ns.advanced-policy-demo   k8s_ns.advanced-policy-demo
 k8s_ns.default                k8s_ns.default
-k8s_ns.kube-public            k8s_ns.kube-public 
+k8s_ns.kube-public            k8s_ns.kube-public
 k8s_ns.kube-system            k8s_ns.kube-system
 ```
 
@@ -157,7 +157,7 @@ It now shows up as a [Policy]({{site.baseurl}}/{{page.version}}/reference/calico
 $ calicoctl get policy -o wide
 NAME                                ORDER   SELECTOR
 advanced-policy-demo.access-nginx   1000    calico/k8s_ns == 'advanced-policy-demo' && run == 'nginx'
-advanced-policy-demo.default-deny   1000    calico/k8s_ns == 'advanced-policy-demo' 
+advanced-policy-demo.default-deny   1000    calico/k8s_ns == 'advanced-policy-demo'
 ```
 
 After creating the policy, we can now access the nginx Service.  We also see that the pod can

master/getting-started/kubernetes/tutorials/using-calicoctl.md

@@ -16,21 +16,21 @@ machine with access to your etcd cluster by setting `ETCD_ENDPOINTS`. For exampl
 ETCD_ENDPOINTS=http://etcd:2379 calicoctl get profile
 ```
 
->**Note for kubeadm deployments**
+> **NOTE for kubeadm deployments**
 >
 > Calico is not configured to use the etcd run by kubeadm on the Kubernetes master.
 > Instead, it launches its own instance of etcd as a pod, available at
-`http://10.96.232.136:6666`.
->Ensure you are connecting to the correct etcd or you will not see any of the expected data.
+> `http://10.96.232.136:6666`.
+> Ensure you are connecting to the correct etcd or you will not see any of the expected data.
 
 ### b. Running calicoctl as a Kubernetes Pod
 
 The `calico/ctl` docker image can be deployed as a pod and used to run calicoctl
 commands. This pod will need to be configured for the Kubernetes environment it is in.
 
->**Note**
+> **NOTE**
 >
->When calicoctl is run as a Pod, the `calicoctl node ...` suite of commands is not available.
+> When calicoctl is run as a Pod, the `calicoctl node ...` suite of commands is not available.
 
 
 For the **etcd backend** (e.g. kubeadm):

master/getting-started/kubernetes/upgrade.md

@@ -199,7 +199,7 @@ spec:
   podSelector:
 ```
 
-> **Note**:
+> **NOTE**
 >
 > The above steps should be followed when upgrading to Calico v2.3.0+ using the Kubernetes
 > datastore driver, and Calico v2.4.0+ using the etcd datastore,

master/getting-started/mesos/installation/dc-os/index.md

@@ -108,7 +108,9 @@ be restarted to pick up the change. The Framework then performs the following st
        }
    }
    ```
-   >Note: If not running etcd in proxy mode, be sure to change `etcd_endpoints`
+   > **NOTE**
+   >
+   > If not running etcd in proxy mode, be sure to change `etcd_endpoints`
    to your correct etcd endpoint address.
 
 4. Restart the slave process with `systemctl restart dcos-mesos-slave`

master/getting-started/mesos/installation/integration.md

@@ -23,7 +23,9 @@ Calico runs as a Docker container on each host. The `calicoctl` command line too
    sudo ETCD_ENDPOINTS=http://$ETCD_IP:$ETCD_PORT calicoctl node run --node-image=quay.io/calico/node:{{site.data.versions[page.version].first.title}}
    ```
 
-   >Note: Ensure you've set or replaced `$ETCD_IP` and `$ETCD_PORT` to point to
+   > **NOTE**
+   >
+   > Ensure you've set or replaced `$ETCD_IP` and `$ETCD_PORT` to point to
    [your etcd cluster](prerequisites).
 
    Check that `calico/node` is now running:

master/getting-started/mesos/installation/prerequisites.md

@@ -58,7 +58,9 @@ Cluster Store: etcd://10.0.0.1:2379
 By default, Mesos only enables the "Mesos" Containerizer. Ensure
 the Docker Containerizer is also enabled on each Agent.
 
->Note: You may skip this step if you do not plan on using the Docker Containerizer.
+> **NOTE**
+>
+> You may skip this step if you do not plan on using the Docker Containerizer.
 
 If you are using the default `mesos-init-wrapper` from the official Mesos package,
 you can enable the Docker Containerizer with the following command:
@@ -73,7 +75,9 @@ $ systemctl restart mesos-slave.service
 If you are planning to use Calico with the Unified containerizer,
 [enable the CNI Isolator on each agent](http://mesos.apache.org/documentation/latest/cni/#usage)
 
->Note: You may skip this step if you do not plan on using the Unified Containerizer.
+> **NOTE**
+>
+> You may skip this step if you do not plan on using the Unified Containerizer.
 
 When enabling CNI, you will have specified a `network_cni_config_dir`
 and `network_cni_plugins_dir`. We'll refer to these going forward as