Skip to content
Snippets Groups Projects
Unverified Commit 90719a99 authored by lijin-union's avatar lijin-union Committed by GitHub
Browse files

Fix some typos in docs file (#9619)

parent 93f71df6
No related branches found
No related tags found
No related merge requests found
...@@ -290,7 +290,7 @@ two projects which are now joined under the Ansible umbrella. ...@@ -290,7 +290,7 @@ two projects which are now joined under the Ansible umbrella.
Ansible-base (2.10.x branch) will contain just the ansible language implementation while Ansible-base (2.10.x branch) will contain just the ansible language implementation while
ansible modules that were previously bundled into a single repository will be part of the ansible modules that were previously bundled into a single repository will be part of the
ansible 3.x package. Pleasee see [this blog post](https://blog.while-true-do.io/ansible-release-3-0-0/) ansible 3.x package. Please see [this blog post](https://blog.while-true-do.io/ansible-release-3-0-0/)
that explains in detail the need and the evolution plan. that explains in detail the need and the evolution plan.
**Note:** this change means that ansible virtual envs cannot be upgraded with `pip install -U`. **Note:** this change means that ansible virtual envs cannot be upgraded with `pip install -U`.
......
...@@ -259,7 +259,7 @@ See [dns_etchosts](#dns_etchosts-coredns) above. ...@@ -259,7 +259,7 @@ See [dns_etchosts](#dns_etchosts-coredns) above.
### Nodelocal DNS HA ### Nodelocal DNS HA
Under some circumstances the single POD nodelocaldns implementation may not be able to be replaced soon enough and a cluster upgrade or a nodelocaldns upgrade can cause DNS requests to time out for short intervals. If for any reason your applications cannot tollerate this behavior you can enable a redundant nodelocal DNS pod on each node: Under some circumstances the single POD nodelocaldns implementation may not be able to be replaced soon enough and a cluster upgrade or a nodelocaldns upgrade can cause DNS requests to time out for short intervals. If for any reason your applications cannot tolerate this behavior you can enable a redundant nodelocal DNS pod on each node:
```yaml ```yaml
enable_nodelocaldns_secondary: true enable_nodelocaldns_secondary: true
......
...@@ -55,7 +55,7 @@ Docker log options: ...@@ -55,7 +55,7 @@ Docker log options:
docker_log_opts: "--log-opt max-size=50m --log-opt max-file=5" docker_log_opts: "--log-opt max-size=50m --log-opt max-file=5"
``` ```
Changre the docker `bin_dir`, this should not be changed unless you use a custom docker package: Change the docker `bin_dir`, this should not be changed unless you use a custom docker package:
```yaml ```yaml
docker_bin_dir: "/usr/bin" docker_bin_dir: "/usr/bin"
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment