From f024de7d3df8897f50976abbbebeb2839a6a93e7 Mon Sep 17 00:00:00 2001
From: Noah Kantrowitz <noah@coderanger.net>
Date: Mon, 25 Mar 2019 16:00:24 -0700
Subject: [PATCH] Typo fix in a docs link. (#13405)

---
 content/en/blog/_posts/2019-03-25-1-14-release-announcement.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/blog/_posts/2019-03-25-1-14-release-announcement.md b/content/en/blog/_posts/2019-03-25-1-14-release-announcement.md
index 727b021c65..448309ba3a 100644
--- a/content/en/blog/_posts/2019-03-25-1-14-release-announcement.md
+++ b/content/en/blog/_posts/2019-03-25-1-14-release-announcement.md
@@ -34,7 +34,7 @@ The new kubectl logo and mascot (pronounced _kubee-cuddle_) are shown on the new
 
 **Kustomize Integration**
 
-The declarative Resource Config authoring capabilities of [kustomize](https://github.com/kubernetes-sigs/kustomize) are now available in kubectl through the `-k` flag (e.g. for commands like `apply, get`) and the `kustomize` subcommand.  Kustomize helps users author and reuse Resource Config using Kubernetes native concepts. Users can now apply directories with `kustomization.yaml` to a cluster using `kubectl apply -k dir/`. Users can also emit customized Resource Config to stdout without applying them via `kubectl kustomize dir/`. The new capabilities are documented in the new docs at https://kubect.docs.kubernetes.io
+The declarative Resource Config authoring capabilities of [kustomize](https://github.com/kubernetes-sigs/kustomize) are now available in kubectl through the `-k` flag (e.g. for commands like `apply, get`) and the `kustomize` subcommand.  Kustomize helps users author and reuse Resource Config using Kubernetes native concepts. Users can now apply directories with `kustomization.yaml` to a cluster using `kubectl apply -k dir/`. Users can also emit customized Resource Config to stdout without applying them via `kubectl kustomize dir/`. The new capabilities are documented in the new docs at https://kubectl.docs.kubernetes.io
 
 The kustomize subcommand will continue to be developed in the Kubernetes owned [kustomize](https://github.com/kubernetes-sigs/kustomize) repo. The latest kustomize features will be available from a standalone kustomize binary (published to the kustomize repo) at a frequent release cadence, and will be updated in kubectl prior to each Kubernetes releases.