sync custom-resource-definitions define-environment-variable-container

Author: asa3311

content/zh-cn/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md

@@ -611,12 +611,12 @@ Notice that the field `someRandomField` was pruned.
 <!--
 This example turned off client-side validation to demonstrate the API server's behavior, by adding
 the `--validate=false` command line option.
-Because the [OpenAPI validation schemas are also published](#publish-validation-schema-in-openapi-v2)
+Because the [OpenAPI validation schemas are also published](#publish-validation-schema-in-openapi)
 to clients, `kubectl` also checks for unknown fields and rejects those objects well before they
 would be sent to the API server.
 -->
 本例中通过 `--validate=false` 命令行选项 关闭了客户端的合法性检查以展示 API 服务器的行为，
-因为 [OpenAPI 合法性检查模式也会发布到](#publish-validation-schema-in-openapi-v2)
+因为 [OpenAPI 合法性检查模式也会发布到](#publish-validation-schema-in-openapi)
 客户端，`kubectl` 也会检查未知的字段并在对象被发送到 API
 服务器之前就拒绝它们。
 
@@ -770,12 +770,12 @@ allOf:
 <!--
 With one of those specification, both an integer and a string validate.
 
-In [Validation Schema Publishing](#publish-validation-schema-in-openapi-v2),
+In [Validation Schema Publishing](#publish-validation-schema-in-openapi),
 `x-kubernetes-int-or-string: true` is unfolded to one of the two patterns shown above.
 -->
 在以上两种规约中，整数值和字符串值都会被认为是合法的。
 
-在[合法性检查模式定义的发布时](#publish-validation-schema-in-openapi-v2)，
+在[合法性检查模式定义的发布时](#publish-validation-schema-in-openapi)，
 `x-kubernetes-int-or-string: true` 会被展开为上述两种模式之一。
 
 ### RawExtension

content/zh-cn/docs/tasks/inject-data-application/define-environment-variable-container.md

@@ -155,21 +155,23 @@ the list. Similarly, avoid circular references.
 <!--
 ## Using environment variables inside of your config
 
-Environment variables that you define in a Pod's configuration can be used
-elsewhere in the configuration, for example in commands and arguments that
-you set for the Pod's containers.
+Environment variables that you define in a Pod's configuration under 
+`.spec.containers[*].env[*]` can be used elsewhere in the configuration, for 
+example in commands and arguments that you set for the Pod's containers.
 In the example configuration below, the `GREETING`, `HONORIFIC`, and
 `NAME` environment variables are set to `Warm greetings to`, `The Most
-Honorable`, and `Kubernetes`, respectively. Those environment variables
-are then used in the CLI arguments passed to the `env-print-demo`
-container.
+Honorable`, and `Kubernetes`, respectively. The environment variable 
+`MESSAGE` combines the set of all these environment variables and then uses it 
+as a CLI argument passed to the `env-print-demo` container.
 -->
 ## 在配置中使用环境变量   {#using-env-var-inside-of-your-config}
 
-你在 Pod 的配置中定义的环境变量可以在配置的其他地方使用，
-例如可用在为 Pod 的容器设置的命令和参数中。
+你在 Pod 的配置中定义的、位于 `.spec.containers[*].env[*]` 下的环境变量
+可以在配置的其他地方使用，例如可用在为 Pod 的容器设置的命令和参数中。
 在下面的示例配置中，环境变量 `GREETING`、`HONORIFIC` 和 `NAME` 分别设置为 `Warm greetings to`、
-`The Most Honorable` 和 `Kubernetes`。然后这些环境变量在传递给容器 `env-print-demo` 的 CLI 参数中使用。
+`The Most Honorable` 和 `Kubernetes`。
+环境变量 `MESSAGE` 将所有这些环境变量的集合组合起来，
+然后再传递给容器 `env-print-demo` 的 CLI 参数中使用。
 
 ```yaml
 apiVersion: v1