fixing broken note annotation, and cleaning blank line endings (#5360)

* fixing broken note annotation, and cleaning blank line endings

* fixing caution annotation typo
pull/5552/head
Joseph Heck 2017-09-08 21:20:29 -07:00 committed by Steve Perry
parent 511402d8e2
commit c4fde406f0
1 changed files with 9 additions and 9 deletions

View File

@ -68,7 +68,7 @@ Next, deploy your cluster with one of two methods:
* [kubespray-cli tool](https://github.com/kubernetes-incubator/kubespray/blob/master/docs/getting-started.md) * [kubespray-cli tool](https://github.com/kubernetes-incubator/kubespray/blob/master/docs/getting-started.md)
**Note:** kubespray-cli is no longer actively maintained. **Note:** kubespray-cli is no longer actively maintained.
{. :note} {: .note}
Both methods run the default [cluster definition file](https://github.com/kubernetes-incubator/kubespray/blob/master/cluster.yml). Both methods run the default [cluster definition file](https://github.com/kubernetes-incubator/kubespray/blob/master/cluster.yml).
@ -99,7 +99,7 @@ Check out planned work on Kubespray's [roadmap](https://github.com/kubernetes-in
You can reset your nodes and wipe out all components installed with Kubespray via the [reset playbook](https://github.com/kubernetes-incubator/kubespray/blob/master/reset.yml). You can reset your nodes and wipe out all components installed with Kubespray via the [reset playbook](https://github.com/kubernetes-incubator/kubespray/blob/master/reset.yml).
**Caution:** When running the reset playbook, be sure not to accidentally target your production cluster! **Caution:** When running the reset playbook, be sure not to accidentally target your production cluster!
{. :caution} {: .caution}
## Feedback ## Feedback