Merge pull request #5964 from zhangxiaoyu-zidif/update-title

Update repo name

docs/concepts/cluster-administration/manage-deployment.md

@@ -9,7 +9,7 @@ title: Managing Resources
 You've deployed your application and exposed it via a service. Now what? Kubernetes provides a number of tools to help you manage your application deployment, including scaling and updating. Among the features that we will discuss in more depth are [configuration files](/docs/concepts/configuration/overview/) and [labels](/docs/concepts/overview/working-with-objects/labels/).
 
 You can find all the files for this example [in our docs
-repo here](https://github.com/kubernetes/kubernetes.github.io/tree/{{page.docsbranch}}/docs/user-guide/).
+repo here](https://github.com/kubernetes/website/tree/{{page.docsbranch}}/docs/user-guide/).
 
 * TOC
 {:toc}

docs/concepts/configuration/assign-pod-node.md

@@ -16,7 +16,7 @@ that a pod ends up on a machine with an SSD attached to it, or to co-locate pods
 services that communicate a lot into the same availability zone.
 
 You can find all the files for these examples [in our docs
-repo here](https://github.com/kubernetes/kubernetes.github.io/tree/{{page.docsbranch}}/docs/user-guide/node-selection).
+repo here](https://github.com/kubernetes/website/tree/{{page.docsbranch}}/docs/user-guide/node-selection).
 
 * TOC
 {:toc}

docs/concepts/workloads/controllers/deployment.md

@@ -58,7 +58,7 @@ The `template` field contains the following instructions:
 To create this Deployment, run the following command:
 
 ```shell
-kubectl create -f https://raw.githubusercontent.com/kubernetes/kubernetes.github.io/master/docs/concepts/workloads/controllers/nginx-deployment.yaml
+kubectl create -f https://raw.githubusercontent.com/kubernetes/website/master/docs/concepts/workloads/controllers/nginx-deployment.yaml
 ```
 
 Note: You can append `--record` to this command to record the current command in the annotations of

docs/getting-started-guides/centos/centos_manual_config.md

@@ -7,7 +7,7 @@ title: CentOS
 * TOC
 {:toc}
 
-**Caution:** This guide was originally written for Kubernetes 1.1.0 and [is deprecated](https://github.com/kubernetes/kubernetes.github.io/issues/1613) and is replaced by [kubeadm](/docs/admin/kubeadm/).
+**Caution:** This guide was originally written for Kubernetes 1.1.0 and [is deprecated](https://github.com/kubernetes/website/issues/1613) and is replaced by [kubeadm](/docs/admin/kubeadm/).
 {: .caution}
 
 ## Prerequisites

docs/home/contribute/create-pull-request.md

@@ -5,7 +5,7 @@ title: Creating a Documentation Pull Request
 {% capture overview %}
 
 To contribute to the Kubernetes documentation, create a pull request against the
-[kubernetes/kubernetes.github.io](https://github.com/kubernetes/kubernetes.github.io){: target="_blank"}
+[kubernetes/website](https://github.com/kubernetes/website){: target="_blank"}
 repository. This page shows how to create a pull request.
 
 {% endcapture %}
@@ -26,7 +26,7 @@ Documentation will be published under the [CC BY SA 4.0](https://git.k8s.io/kube
 ## Creating a fork of the Kubernetes documentation repository
 
 1. Go to the
-[kubernetes/kubernetes.github.io](https://github.com/kubernetes/kubernetes.github.io){: target="_blank"}
+[kubernetes/website](https://github.com/kubernetes/website){: target="_blank"}
 repository.
 
 1. In the upper-right corner, click **Fork**. This creates a copy of the
@@ -51,7 +51,7 @@ create a pull request against the master branch of the Kubernetes
 documentation repository.
 
 1. In your GitHub account, in your new branch, create a pull request
-against the master branch of the kubernetes/kubernetes.github.io
+against the master branch of the kubernetes/website
 repository. This opens a page that shows the status of your pull request.
 
 1. Click **Show all checks**. Wait for the **deploy/netlify** check to complete.
@@ -70,7 +70,7 @@ of the Kubernetes documentation repository. The <vnext> branch has the
 form `release-<version-number>`, for example release-1.5.
 
 1. In your GitHub account, in your new branch, create a pull request
-against the &lt;vnext&gt; branch of the kubernetes/kubernetes.github.io
+against the &lt;vnext&gt; branch of the kubernetes/website
 repository. This opens a page that shows the status of your pull request.
 
 1. Click **Show all checks**. Wait for the **deploy/netlify** check to complete.

docs/home/contribute/page-templates.md

@@ -13,7 +13,7 @@ title: Using Page Templates
     <li><a href="#concept_template">Concept</a></li>
 </ul>
 
-<p>The page templates are in the <a href="https://git.k8s.io/kubernetes.github.io/_includes/templates" target="_blank">_includes/templates</a> directory of the <a href="https://github.com/kubernetes/kubernetes.github.io">kubernetes.github.io</a> repository.
+<p>The page templates are in the <a href="https://git.k8s.io/kubernetes.github.io/_includes/templates" target="_blank">_includes/templates</a> directory of the <a href="https://github.com/kubernetes/website">kubernetes.github.io</a> repository.
 
 <h2 id="task_template">Task template</h2>
 

docs/home/contribute/review-issues.md

@@ -4,7 +4,7 @@ title: Reviewing Documentation Issues
 
 {% capture overview %}
 
-This page explains how documentation issues are reviewed and prioritized for the [kubernetes/kubernetes.github.io](https://github.com/kubernetes/kubernetes.github.io){: target="_blank"} repository. The purpose is to provide a way to organize issues and make it easier to contribute to Kubernetes documentation. The following should be used as the standard way of prioritizing, labeling, and interacting with issues.
+This page explains how documentation issues are reviewed and prioritized for the [kubernetes/website](https://github.com/kubernetes/website){: target="_blank"} repository. The purpose is to provide a way to organize issues and make it easier to contribute to Kubernetes documentation. The following should be used as the standard way of prioritizing, labeling, and interacting with issues.
 {% endcapture %}
 
 {% capture body %}

docs/home/contribute/stage-documentation-changes.md

@@ -21,7 +21,7 @@ branch, your changes are staged in a custom subdomain on Netlify so that
 you can see your changes in rendered form before the pull request is merged.
 
 1. In your GitHub account, in your new branch, submit a pull request to the
-kubernetes/kubernetes.github.io repository. This opens a page that shows the
+kubernetes/website repository. This opens a page that shows the
 status of your pull request.
 
 1. Scroll down to the list of automated checks. Click **Show all checks**.