Merge pull request #45341 from asa3311/sync-zh-100

[zh] sync blogs-case-studies multiple-zones

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

@@ -219,6 +219,10 @@ Submissions need to be in Markdown format to be used by the [Hugo](https://gohug
 for the blog. There are [many resources available](https://gohugo.io/documentation/) on how to use
 this technology stack.
 
+For illustrations, diagrams or charts, the [figure shortcode](https://gohugo.io/content-management/shortcodes/#figure)
+can be used. For other images, we strongly encourage use of alt attributes; if an image doesn't
+need any alt attrribute, maybe it's not needed in the article at all.
+
 We recognize that this requirement makes the process more difficult for less-familiar folks to
 submit, and we're constantly looking at solutions to lower this bar. If you have ideas on how to
 lower the barrier, please volunteer to help out. 
@@ -228,6 +232,10 @@ lower the barrier, please volunteer to help out.
 所提交的内容应该是 Markdown 格式的，以便能够被 [Hugo](https://gohugo.io/) 生成器来处理。
 关于如何使用相关技术，有[很多可用的资源](https://gohugo.io/documentation/)。
 
+对于插图、表格或图表，可以使用 [figure shortcode](https://gohugo.io/content-management/shortcodes/#figure)。
+对于其他图片，我们强烈建议使用 alt 属性；如果一张图片不需要任何 alt 属性，
+那么这张图片在文章中就不是必需的。
+
 我们知道这一需求可能给那些对此过程不熟悉的朋友们带来不便，
 我们也一直在寻找降低难度的解决方案。
 如果你有降低难度的好主意，请自荐帮忙。

content/zh-cn/docs/setup/best-practices/multiple-zones.md

@@ -185,22 +185,26 @@ such as Deployment, StatefulSet, or Job.
 <!--
 ## Storage access for zones
 
-When persistent volumes are created, the `PersistentVolumeLabel`
-[admission controller](/docs/reference/access-authn-authz/admission-controllers/)
-automatically adds zone labels to any PersistentVolumes that are linked to a specific
-zone. The {{< glossary_tooltip text="scheduler" term_id="kube-scheduler" >}} then ensures,
+When persistent volumes are created, Kubernetes automatically adds zone labels 
+to any PersistentVolumes that are linked to a specific zone.
+The {{< glossary_tooltip text="scheduler" term_id="kube-scheduler" >}} then ensures,
 through its `NoVolumeZoneConflict` predicate, that pods which claim a given PersistentVolume
 are only placed into the same zone as that volume.
+
+Please note that the method of adding zone labels can depend on your 
+cloud provider and the storage provisioner you’re using. Always refer to the specific 
+documentation for your environment to ensure correct configuration.
 -->
 ## 跨区的存储访问
 
-当创建持久卷时，`PersistentVolumeLabel` 
-[准入控制器](/zh-cn/docs/reference/access-authn-authz/admission-controllers/)
-会自动向那些链接到特定区的 PersistentVolume 添加区标签。
+当创建持久卷时，Kubernetes 会自动向那些链接到特定区的 PersistentVolume 添加区标签。。
 {{< glossary_tooltip text="调度器" term_id="kube-scheduler" >}}通过其
 `NoVolumeZoneConflict` 断言确保申领给定 PersistentVolume 的 Pods 只会
 被调度到该卷所在的可用区。
 
+请注意，添加区标签的方法可能会根据你所使用的云提供商和存储制备器而有所不同。
+为确保配置正确，请始终参阅你的环境的特定文档。
+
 <!--
 You can specify a {{< glossary_tooltip text="StorageClass" term_id="storage-class" >}}
 for PersistentVolumeClaims that specifies the failure domains (zones) that the