Merge pull request #26229 from rikatz/spell-correction
Fix some spell checking
This commit is contained in:
@@ -255,7 +255,7 @@ To migrate from kube-dns to CoreDNS, a detailed
|
||||
[blog article](https://coredns.io/2018/05/21/migration-from-kube-dns-to-coredns/)
|
||||
is available to help users adapt CoreDNS in place of kube-dns.
|
||||
|
||||
You can also migrate using the offical CoreDNS
|
||||
You can also migrate using the official CoreDNS
|
||||
[deploy script](https://github.com/coredns/deployment/blob/master/kubernetes/deploy.sh).
|
||||
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ _Topology Manager_ is a Kubelet component that aims to co-ordinate the set of co
|
||||
|
||||
|
||||
|
||||
## {{% heading "prerequisites" %}}
|
||||
## {{% heading "prerequisites" %}}
|
||||
|
||||
|
||||
{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
|
||||
@@ -192,7 +192,7 @@ spec:
|
||||
|
||||
This pod runs in the `Burstable` QoS class because requests are less than limits.
|
||||
|
||||
If the selected policy is anything other than `none`, Topology Manager would consider these Pod specifications. The Topology Manager would consult the Hint Providers to get topology hints. In the case of the `static`, the CPU Manager policy would return default topology hint, because these Pods do not have explicity request CPU resources.
|
||||
If the selected policy is anything other than `none`, Topology Manager would consider these Pod specifications. The Topology Manager would consult the Hint Providers to get topology hints. In the case of the `static`, the CPU Manager policy would return default topology hint, because these Pods do not have explicitly request CPU resources.
|
||||
|
||||
|
||||
```yaml
|
||||
|
||||
Reference in New Issue
Block a user