[zh]sync contribution files for 1.22(Part-1)

content/zh/docs/contribute/new-content/blogs-case-studies.md

@@ -101,7 +101,7 @@ Kubernetes 博客用于项目发布新功能特性、社区报告以及其他一
 <!--
 - Blog posts should be original content
   - The official blog is not for repurposing existing content from a third party as new content.
-  - The [license](https://github.com/kubernetes/website/blob/master/LICENSE) for the blog allows commercial use of the content for commercial purposes, just not the other way around. 
+  - The [license](https://github.com/kubernetes/website/blob/main/LICENSE) for the blog allows commercial use of the content for commercial purposes, just not the other way around. 
 - Blog posts should aim to be future proof
   - Given the development velocity of the project, we want evergreen content that won't require updates to stay accurate for the reader. 
   - It can be a better choice to add a tutorial or update official documentation than to write a high level overview as a blog post.
@@ -109,7 +109,7 @@ Kubernetes 博客用于项目发布新功能特性、社区报告以及其他一
 -->
 - 博客文章应该是原创内容。
   - 官方博客的目的不是将某第三方已发表的内容重新作为新内容发表。
-  - 博客的[授权协议](https://github.com/kubernetes/website/blob/master/LICENSE)
+  - 博客的[授权协议](https://github.com/kubernetes/website/blob/main/LICENSE)
     的确允许出于商业目的来使用博客内容；但并不是所有可以商用的内容都适合在这里发表。
 - 博客文章的内容应该在一段时间内不过期。
   - 考虑到项目的开发速度，我们希望读者看到的是不必更新就能保持长期准确的内容。 
@@ -144,7 +144,7 @@ SIG Docs [博客子项目](https://github.com/kubernetes/community/tree/master/s
 
 要提交博文，你可以遵从以下指南：
 <!--
-- [Open a pull request](/docs/contribute/new-content/open-a-pr/#fork-the-repo) with a new blog post. New blog posts go under the [`content/en/blog/_posts`](https://github.com/kubernetes/website/tree/master/content/en/blog/_posts) directory.
+- [Open a pull request](/docs/contribute/new-content/open-a-pr/#fork-the-repo) with a new blog post. New blog posts go under the [`content/en/blog/_posts`](https://github.com/kubernetes/website/tree/main/content/en/blog/_posts) directory.
 
 - Ensure that your blog post follows the correct naming conventions and the following frontmatter (metadata) information:
 
@@ -153,7 +153,7 @@ SIG Docs [博客子项目](https://github.com/kubernetes/community/tree/master/s
   - The front matter must include the following:
 -->
 - [发起一个包含博文的 PR](/zh/docs/contribute/new-content/open-a-pr/#fork-the-repo)。
-  新博文要创建于 [`content/en/blog/_posts`](https://github.com/kubernetes/website/tree/master/content/en/blog/_posts) 目录下。
+  新博文要创建于 [`content/en/blog/_posts`](https://github.com/kubernetes/website/tree/main/content/en/blog/_posts) 目录下。
 
 - 确保你的博文遵从合适的命名规范，并带有下面的引言（元数据）信息：
 
@@ -205,7 +205,7 @@ Case studies highlight how organizations are using Kubernetes to solve
 real-world problems. The Kubernetes marketing team and members of the {{< glossary_tooltip text="CNCF" term_id="cncf" >}} collaborate with you on all case studies.
 
 Have a look at the source for the
-[existing case studies](https://github.com/kubernetes/website/tree/master/content/en/case-studies).
+[existing case studies](https://github.com/kubernetes/website/tree/main/content/en/case-studies).
 
 Refer to the [case study guidelines](https://github.com/cncf/foundation/blob/master/case-study-guidelines.md) and submit your request as outlined in the guidelines. 
 -->
@@ -216,7 +216,7 @@ Kubernetes 市场化团队和 {{< glossary_tooltip text="CNCF" term_id="cncf" >}
 会与你一起工作，撰写所有的案例分析。
 
 请查看
-[现有案例分析](https://github.com/kubernetes/website/tree/master/content/en/case-studies)
+[现有案例分析](https://github.com/kubernetes/website/tree/main/content/en/case-studies)
 的源码。
 
 参考[案例分析指南](https://github.com/cncf/foundation/blob/master/case-study-guidelines.md)