Merge pull request #39386 from fenggw-fnst/typo

Fix some typos

Author: k8s-ci-robot

content/en/blog/_posts/2016-10-00-Dynamic-Provisioning-And-Storage-In-Kubernetes.md

@@ -143,7 +143,7 @@ When a default StorageClass exists and a user creates a PersistentVolumeClaim wi
 
 
 
-Kubernetes 1.4 maintains backwards compatibility with the alpha version of the dynamic provisioning feature to allow for a smoother transition to the beta version. The alpha behavior is triggered by the existance of the alpha dynamic provisioning annotation (volume. **alpha**.kubernetes.io/storage-class). Keep in mind that if the beta annotation (volume. **beta**.kubernetes.io/storage-class) is present, it takes precedence, and triggers the beta behavior.
+Kubernetes 1.4 maintains backwards compatibility with the alpha version of the dynamic provisioning feature to allow for a smoother transition to the beta version. The alpha behavior is triggered by the existence of the alpha dynamic provisioning annotation (volume. **alpha**.kubernetes.io/storage-class). Keep in mind that if the beta annotation (volume. **beta**.kubernetes.io/storage-class) is present, it takes precedence, and triggers the beta behavior.
 
 
 

content/en/blog/_posts/2018-06-28-Airflow-Kubernetes-Operator.md

@@ -192,7 +192,7 @@ To modify/add your own DAGs, you can use `kubectl cp` to upload local files into
 
 # Get Involved
 
-This feature is just the beginning of multiple major efforts to improves Apache Airflow integration into Kubernetes. The Kubernetes Operator has been merged into the [1.10 release branch of Airflow](https://github.com/apache/incubator-airflow/tree/v1-10-test) (the executor in experimental mode), along with a fully k8s native scheduler called the Kubernetes Executor (article to come). These features are still in a stage where early adopters/contributers can have a huge influence on the future of these features.
+This feature is just the beginning of multiple major efforts to improves Apache Airflow integration into Kubernetes. The Kubernetes Operator has been merged into the [1.10 release branch of Airflow](https://github.com/apache/incubator-airflow/tree/v1-10-test) (the executor in experimental mode), along with a fully k8s native scheduler called the Kubernetes Executor (article to come). These features are still in a stage where early adopters/contributors can have a huge influence on the future of these features.
 
 For those interested in joining these efforts, I'd recommend checkint out these steps:
 

content/en/blog/_posts/2018-10-02-network-bootable-farm-with-ltsp.md

@@ -460,7 +460,7 @@ Now you can configure your DHCP. Basically you should set the `next-server` and
 I use ISC-DHCP server, and here is an example `dhcpd.conf`:
 
 ```
-shared-network ltsp-netowrk {
+shared-network ltsp-network {
     subnet 10.9.0.0 netmask 255.255.0.0 {
         authoritative;
         default-lease-time -1;

content/en/blog/_posts/2020-05-06-third-party-dual-sourced-content.md

@@ -27,7 +27,7 @@ Our goal is for Kubernetes docs to be a trustworthy guide to Kubernetes features
 
 ### Re-homing content
 
-Some content will be removed that readers may find helpful. To make sure readers have continous access to information, we're giving stakeholders until the [1.19 release deadline for docs](https://github.com/kubernetes/sig-release/tree/master/releases/release-1.19), **July 9th, 2020** to re-home any content slated for removal.
+Some content will be removed that readers may find helpful. To make sure readers have continuous access to information, we're giving stakeholders until the [1.19 release deadline for docs](https://github.com/kubernetes/sig-release/tree/master/releases/release-1.19), **July 9th, 2020** to re-home any content slated for removal.
 
 Over the next few months you'll see less third party content in the docs as contributors open PRs to remove content.
 

content/en/blog/_posts/2020-05-21-wsl2-dockerdesktop-k8s.md

@@ -520,7 +520,7 @@ And the real strength of WSL2 integration, the port `8443` once open on WSL2 dis
 
 Working on the command line is always good and very insightful. However, when dealing with Kubernetes we might want, at some point, to have a visual overview.
 
-For that, Minikube embeded the [Kubernetes Dashboard](https://github.com/kubernetes/dashboard). Thanks to it, running and accessing the Dashboard is very simple:
+For that, Minikube embedded the [Kubernetes Dashboard](https://github.com/kubernetes/dashboard). Thanks to it, running and accessing the Dashboard is very simple:
 
 ```bash
 # Enable the Dashboard service

content/en/blog/_posts/2020-07-27-kubernetes-1-17-release-interview.md

@@ -198,7 +198,7 @@ GUINEVERE SAENGER: I would want Jorge to be really on top of making sure that ev
 
 Greater communication of timelines and just giving people more time and space to be able to get in their changes, or at least, seemingly give them more time and space by sending early warnings, is going to be helpful. Of course, he's going to have a slightly longer release, too, than I did. This might be related to a unique Q4 challenge. Overall, I would encourage him to take more breaks, to rely more on his release shadows, and split out the work in a fashion that allows everyone to have a turn and everyone to have a break as well.
 
-**ADAM GLICK: What would your advice be to someone who is hearing your experience and is inspired to get involved with the Kubernetes release or contributer process?**
+**ADAM GLICK: What would your advice be to someone who is hearing your experience and is inspired to get involved with the Kubernetes release or contributor process?**
 
 GUINEVERE SAENGER: Those are two separate questions. So let me tackle the Kubernetes release question first. Kubernetes [SIG Release](https://github.com/kubernetes/sig-release/#readme) has, in my opinion, a really excellent onboarding program for new members. We have what is called the [Release Team Shadow Program](https://github.com/kubernetes/sig-release/blob/master/release-team/shadows.md). We also have the Release Engineering Shadow Program, or the Release Management Shadow Program. Those are two separate subprojects within SIG Release. And each subproject has a team of roles, and each role can have two to four shadows that are basically people who are part of that role team, and they are learning that role as they are doing it.
 

content/en/blog/_posts/2021-12-07-kubernetes-release-1.23.md

@@ -81,7 +81,7 @@ If the `ServerSideFieldValidation` feature gate is enabled starting 1.23, users
 
 With the feature gate enabled, we also introduce the `fieldValidation` query parameter so that users can specify the desired behavior of the server on a per request basis. Valid values for the `fieldValidation` query parameter are:
 
-- Ignore (default when feature gate is disabled, same as pre-1.23 behavior of dropping/ignoring unkonwn fields)
+- Ignore (default when feature gate is disabled, same as pre-1.23 behavior of dropping/ignoring unknown fields)
 - Warn (default when feature gate is enabled).
 - Strict (this will fail the request with an Invalid Request error)
 

content/en/blog/_posts/2022-03-15-meet-our-contributors-APAC-AU-NZ-region-02.md

@@ -32,7 +32,7 @@ Caleb is also a co-organizer of the [CloudNative NZ](https://www.meetup.com/clou
 
 ## [Dylan Graham](https://github.com/DylanGraham)
 
-Dylan Graham is a cloud engineer from Adeliade, Australia. He has been contributing to the upstream Kubernetes project since 2018.
+Dylan Graham is a cloud engineer from Adelaide, Australia. He has been contributing to the upstream Kubernetes project since 2018.
 
 He stated that being a part of such a large-scale project was initially overwhelming, but that the community's friendliness and openness assisted him in getting through it.
 

content/en/blog/_posts/2022-05-27-maxunavailable-for-statefulset.md

@@ -18,7 +18,7 @@ case where you're using the `OrderedReady` Pod management policy for a StatefulS
 Here are some examples:
 
 -  I am using a StatefulSet to orchestrate a multi-instance, cache based application where the size of the cache is large. The cache 
-   starts cold and requires some siginificant amount of time before the container can start. There could be more initial startup tasks
+   starts cold and requires some significant amount of time before the container can start. There could be more initial startup tasks
    that are required. A RollingUpdate on this StatefulSet would take a lot of time before the application is fully updated. If the 
    StatefulSet supported updating more than one pod at a time, it would result in a much faster update.
 

content/en/blog/_posts/2022-08-31-cgroupv2-ga.md

@@ -89,7 +89,7 @@ To use cgroup v2 with Kubernetes, you must meet the following requirements:
 * The kubelet and the container runtime are configured to use the [systemd cgroup driver](/docs/setup/production-environment/container-runtimes#systemd-cgroup-driver)
 
 The kubelet and container runtime use a [cgroup driver](/docs/setup/production-environment/container-runtimes#cgroup-drivers)
-to set cgroup paramaters. When using cgroup v2, it's strongly recommended that both
+to set cgroup parameters. When using cgroup v2, it's strongly recommended that both
 the kubelet and your container runtime use the
 [systemd cgroup driver](/docs/setup/production-environment/container-runtimes#systemd-cgroup-driver),
 so that there's a single cgroup manager on the system. To configure the kubelet