From 668c2b1ca92314f545647251994a9ad6abdc5198 Mon Sep 17 00:00:00 2001 From: Ritikaa96 Date: Tue, 1 Nov 2022 18:13:32 +0530 Subject: [PATCH] correcting grammatical mistakes in migrating-from-dockershim.md --- .../migrating-from-dockershim/_index.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/_index.md b/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/_index.md index b10f75dd9c..6e48d6033e 100644 --- a/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/_index.md +++ b/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/_index.md @@ -16,12 +16,12 @@ installations. Our [Dockershim Removal FAQ](/blog/2022/02/17/dockershim-faq/) is to understand the problem better. Dockershim was removed from Kubernetes with the release of v1.24. -If you use Docker Engine via dockershim as your container runtime, and wish to upgrade to v1.24, +If you use Docker Engine via dockershim as your container runtime and wish to upgrade to v1.24, it is recommended that you either migrate to another runtime or find an alternative means to obtain Docker Engine support. -Check out [container runtimes](/docs/setup/production-environment/container-runtimes/) +Check out the [container runtimes](/docs/setup/production-environment/container-runtimes/) section to know your options. Make sure to [report issues](https://github.com/kubernetes/kubernetes/issues) you encountered -with the migration. So the issue can be fixed in a timely manner and your cluster would be +with the migration so the issues can be fixed in a timely manner and your cluster would be ready for dockershim removal. Your cluster might have more than one kind of node, although this is not a common @@ -37,11 +37,11 @@ These tasks will help you to migrate: ## {{% heading "whatsnext" %}} * Check out [container runtimes](/docs/setup/production-environment/container-runtimes/) - to understand your options for a container runtime. + to understand your options for an alternative. * There is a [GitHub issue](https://github.com/kubernetes/kubernetes/issues/106917) - to track discussion about the deprecation and removal of dockershim. -* If you found a defect or other technical concern relating to migrating away from dockershim, + to track the discussion about the deprecation and removal of dockershim. +* If you find a defect or other technical concern relating to migrating away from dockershim, you can [report an issue](https://github.com/kubernetes/kubernetes/issues/new/choose) to the Kubernetes project.