From f0f7b1128bae9a63c32a27eb98f2e6b1d7bdb922 Mon Sep 17 00:00:00 2001 From: Seth McCombs Date: Thu, 19 Sep 2019 15:07:43 -0700 Subject: [PATCH] blog post typo --- .../_posts/2019-09-18-kubernetes-1-16-release-announcement.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2019-09-18-kubernetes-1-16-release-announcement.md b/content/en/blog/_posts/2019-09-18-kubernetes-1-16-release-announcement.md index c8a749edf3c35..6cdbec97f8149 100644 --- a/content/en/blog/_posts/2019-09-18-kubernetes-1-16-release-announcement.md +++ b/content/en/blog/_posts/2019-09-18-kubernetes-1-16-release-announcement.md @@ -39,7 +39,7 @@ In 1.16 if you submit a `Deployment` to the API server and specify `extensions/v error: unable to recognize "deployment": no matches for kind "Deployment" in version "extensions/v1beta1" ``` -With this release we are taking a very important step in the maturity of the Kubernetes API, and are longer serving the deprecated APIs. Our earlier post [Deprecated APIs Removed In 1.16: Here’s What You Need To Know](https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/) tells you more, including which resources are affected. +With this release we are taking a very important step in the maturity of the Kubernetes API, and are no longer serving the deprecated APIs. Our earlier post [Deprecated APIs Removed In 1.16: Here’s What You Need To Know](https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/) tells you more, including which resources are affected. # Additional Enhancements