[en] Mention kubernetes/websites everywhere in the same way (#40493)

* Mention kubernetes/websites everywhere in the same way

* Acidentially ignored file during replacement

* Apply suggestions from code review

Author: MaxymVlasov

content/en/blog/_posts/2018-11-08-kubernetes-docs-update-i18n.md

@@ -37,7 +37,7 @@ Prow automatically applies language labels based on file path. Thanks to SIG Doc
 /language ko
 ```
 
-These repo labels let reviewers filter for PRs and issues by language. For example, you can now filter the k/website dashboard for [PRs with Chinese content](https://github.com/kubernetes/website/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+label%3Alanguage%2Fzh).  
+These repo labels let reviewers filter for PRs and issues by language. For example, you can now filter the kubernetes/website dashboard for [PRs with Chinese content](https://github.com/kubernetes/website/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+label%3Alanguage%2Fzh).  
 
 ### Team review 
 

content/en/docs/contribute/_index.md

@@ -76,7 +76,7 @@ end
 subgraph second[Review]
 direction TB
    T[ ] -.-
-   D[Look over the<br>K8s/website<br>repository] --- E[Check out the<br>Hugo static site<br>generator]
+   D[Look over the<br>kubernetes/website<br>repository] --- E[Check out the<br>Hugo static site<br>generator]
    E --- F[Understand basic<br>GitHub commands]
    F --- G[Review open PR<br>and change review <br>processes]
 end
@@ -123,7 +123,7 @@ flowchart LR
     direction TB
     S[ ] -.-
     G[Review PRs from other<br>K8s members] -->
-    A[Check K8s/website<br>issues list for<br>good first PRs] --> B[Open a PR!!]
+    A[Check kubernetes/website<br>issues list for<br>good first PRs] --> B[Open a PR!!]
     end
     subgraph first[Suggested Prep]
     direction TB

content/en/docs/contribute/new-content/open-a-pr.md

@@ -37,7 +37,7 @@ opening a pull request. Figure 1 outlines the steps and the details follow.
 
 {{< mermaid >}}
 flowchart LR
-A([fa:fa-user New<br>Contributor]) --- id1[(K8s/Website<br>GitHub)]
+A([fa:fa-user New<br>Contributor]) --- id1[(kubernetes/website<br>GitHub)]
 subgraph tasks[Changes using GitHub]
 direction TB
     0[ ] -.-
@@ -132,7 +132,7 @@ Figure 2 shows the steps to follow when you work from a local fork. The details
 
 {{< mermaid >}}
 flowchart LR
-1[Fork the K8s/website<br>repository] --> 2[Create local clone<br>and set upstream]
+1[Fork the kubernetes/website<br>repository] --> 2[Create local clone<br>and set upstream]
 subgraph changes[Your changes]
 direction TB
 S[ ] -.-
@@ -359,7 +359,9 @@ Alternately, install and use the `hugo` command on your computer:
 
 ### Open a pull request from your fork to kubernetes/website {#open-a-pr}
 
-Figure 3 shows the steps to open a PR from your fork to the K8s/website. The details follow.
+Figure 3 shows the steps to open a PR from your fork to the [kubernetes/website](https://github.com/kubernetes/website). The details follow.
+
+Please, note that contributors can mention `kubernetes/website` as `k/website`.
 
 <!-- See https://github.com/kubernetes/website/issues/28808 for live-editor URL to this figure -->
 <!-- You can also cut/paste the mermaid code into the live editor at https://mermaid-js.github.io/mermaid-live-editor to play around with it -->
@@ -368,7 +370,7 @@ Figure 3 shows the steps to open a PR from your fork to the K8s/website. The det
 flowchart LR
 subgraph first[ ]
 direction TB
-1[1. Go to K8s/website repository] --> 2[2. Select New Pull Request]
+1[1. Go to kubernetes/website repository] --> 2[2. Select New Pull Request]
 2 --> 3[3. Select compare across forks]
 3 --> 4[4. Select your fork from<br>head repository drop-down menu]
 end
@@ -387,7 +389,7 @@ class 1,2,3,4,5,6,7,8 grey
 class first,second white
 {{</ mermaid >}}
 
-Figure 3. Steps to open a PR from your fork to the K8s/website.
+Figure 3. Steps to open a PR from your fork to the [kubernetes/website](https://github.com/kubernetes/website).
 
 1. In a web browser, go to the [`kubernetes/website`](https://github.com/kubernetes/website/) repository.
 1. Select **New Pull Request**.

content/en/docs/contribute/style/diagram-guide.md

@@ -260,7 +260,8 @@ You should use the [local](/docs/contribute/new-content/open-a-pr/#preview-local
 and Netlify previews to verify the diagram is properly rendered. 
 
 {{< caution >}}
-The Mermaid live editor feature set may not support the K8s/website Mermaid feature set. 
+The Mermaid live editor feature set may not support the [kubernetes/website](https://github.com/kubernetes/website) Mermaid feature set.  
+And please, note that contributors can mention `kubernetes/website` as `k/website`.
 You might see a syntax error or a blank screen after the Hugo build.
 If that is the case, consider using the Mermaid+SVG method. 
 {{< /caution >}}
@@ -342,7 +343,7 @@ The following lists advantages of the Mermaid+SVG method:
 
 * Live editor tool.
 * Live editor tool supports the most current Mermaid feature set.  
-* Employ existing K8s/website methods for handling `.svg` image files.
+* Employ existing [kubernetes/website](https://github.com/kubernetes/website) methods for handling `.svg` image files.
 * Environment doesn't require Mermaid support.
 
 Be sure to check that your diagram renders properly using the

content/en/releases/release.md

@@ -4,7 +4,7 @@ type: docs
 auto_generated: true
 ---
 
-<!-- THIS CONTENT IS AUTO-GENERATED via ./scripts/releng/update-release-info.sh in k/website -->
+<!-- THIS CONTENT IS AUTO-GENERATED via ./scripts/releng/update-release-info.sh in kubernetes/website -->
 
 {{< warning >}}
 This content is auto-generated and links may not function. The source of the document is located [here](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-release/release.md).