Merge pull request #376 from Peefy/update-config-pattern

chore: update config pattern

Author: Peefy

docs/user_docs/concepts/type-and-definition.md

@@ -9,7 +9,7 @@ KCL features a **gradual static type system**, initially designed to consider sc
 The configuration of attributes and types in KCL usually follows a simple pattern:
 
 $$
-k = (T) v
+k\ o \ (T) \ v
 $$
 
 where $k$ is the attribute name, $v$ is the attributes value, and $T$ is the type annotation. Since KCL has the ability of the type inference, $T$ is usually omitted.

docs/user_docs/getting-started/intro.md

@@ -65,10 +65,10 @@ While KCL is not a general-purpose language, it excels within its specific domai
 KCL's attribute configuration follows a simple pattern:
 
 $$
-k op (T) v
+k\ o \ (T) \ v
 $$
 
-where $k$ is the attribute name, $v$ is the attributes value, $op$ is the attribute operator and $T$ is the type annotation. Since KCL has the ability of the type inference, $T$ is usually omitted. `deploy = Deployment {}` is a simple example that satisfies the pattern.
+where $k$ is the attribute name, $v$ is the attributes value, $o$ is the attribute operator and $T$ is the type annotation. Since KCL has the ability of the type inference, $T$ is usually omitted. `deploy = Deployment {}` is a simple example that satisfies the pattern.
 
 This is an example of generating Kubernetes manifests.
 

i18n/zh-CN/docusaurus-plugin-content-docs/current/user_docs/concepts/type-and-definition.md

@@ -9,7 +9,7 @@ KCL features a **gradual static type system**, initially designed to consider sc
 The configuration of attributes and types in KCL usually follows a simple pattern:
 
 $$
-k = (T) v
+k\ o \ (T) \ v
 $$
 
 where $k$ is the attribute name, $v$ is the attributes value, and $T$ is the type annotation. Since KCL has the ability of the type inference, $T$ is usually omitted.

i18n/zh-CN/docusaurus-plugin-content-docs/current/user_docs/getting-started/intro.md

@@ -66,10 +66,10 @@ KCL 试图提供独立于运行时的可编程性，不在本地提供线程和
 KCL 配置通常遵循如下模式：
 
 $$
-k op (T) v
+k\ o \ (T) \ v
 $$
 
-其中，$k$ 是属性名称，$v$ 是属性值，$op$ 是属性运算符，$T$ 是类型注解。由于 KCL 具有类型推导的能力，因此 $T$ 通常可以省略。比如 `deploy = Deployment {}` 就是一个符合该模式的简单示例。
+其中，$k$ 是属性名称，$v$ 是属性值，$o$ 是属性运算符，$T$ 是类型注解。由于 KCL 具有类型推导的能力，因此 $T$ 通常可以省略。比如 `deploy = Deployment {}` 就是一个符合该模式的简单示例。
 
 下面是一个用 KCL 生成 Kubernetes 资源的例子
 

i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5/user_docs/concepts/type-and-definition.md

@@ -9,7 +9,7 @@ KCL features a **gradual static type system**, initially designed to consider sc
 The configuration of attributes and types in KCL usually follows a simple pattern:
 
 $$
-k = (T) v
+k\ o \ (T) \ v
 $$
 
 where $k$ is the attribute name, $v$ is the attributes value, and $T$ is the type annotation. Since KCL has the ability of the type inference, $T$ is usually omitted.

i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5/user_docs/getting-started/intro.md

@@ -61,7 +61,7 @@ KCL 试图提供独立于运行时的可编程性，不在本地提供线程和I
 KCL 配置通常遵循如下模式：
 
 $$
-k = (T) v
+k\ o \ (T) \ v
 $$
 
 其中，$k$ 是属性名称，$v$ 是属性值，$T$ 是类型注解。由于 KCL 具有类型推导的能力，因此 $T$ 通常可以省略。

i18n/zh-CN/docusaurus-plugin-content-docs/version-0.6/user_docs/concepts/type-and-definition.md

@@ -9,7 +9,7 @@ KCL features a **gradual static type system**, initially designed to consider sc
 The configuration of attributes and types in KCL usually follows a simple pattern:
 
 $$
-k = (T) v
+k\ o \ (T) \ v
 $$
 
 where $k$ is the attribute name, $v$ is the attributes value, and $T$ is the type annotation. Since KCL has the ability of the type inference, $T$ is usually omitted.

i18n/zh-CN/docusaurus-plugin-content-docs/version-0.6/user_docs/getting-started/intro.md

@@ -64,7 +64,7 @@ KCL 试图提供独立于运行时的可编程性，不在本地提供线程和I
 KCL 配置通常遵循如下模式：
 
 $$
-k = (T) v
+k\ o \ (T) \ v
 $$
 
 其中，$k$ 是属性名称，$v$ 是属性值，$T$ 是类型注解。由于 KCL 具有类型推导的能力，因此 $T$ 通常可以省略。

i18n/zh-CN/docusaurus-plugin-content-docs/version-0.7/user_docs/concepts/type-and-definition.md

@@ -9,7 +9,7 @@ KCL features a **gradual static type system**, initially designed to consider sc
 The configuration of attributes and types in KCL usually follows a simple pattern:
 
 $$
-k = (T) v
+k\ o \ (T) \ v
 $$
 
 where $k$ is the attribute name, $v$ is the attributes value, and $T$ is the type annotation. Since KCL has the ability of the type inference, $T$ is usually omitted.

i18n/zh-CN/docusaurus-plugin-content-docs/version-0.7/user_docs/getting-started/intro.md

@@ -64,7 +64,7 @@ KCL 试图提供独立于运行时的可编程性，不在本地提供线程和I
 KCL 配置通常遵循如下模式：
 
 $$
-k = (T) v
+k\ o \ (T) \ v
 $$
 
 其中，$k$ 是属性名称，$v$ 是属性值，$T$ 是类型注解。由于 KCL 具有类型推导的能力，因此 $T$ 通常可以省略。