mdx: administrator-manual/kubernetes 교정/교열 (KO/EN/JA) (#874)

## Summary

- 한국어 Kubernetes 관리자 매뉴얼 문서의 오타·맞춤법·서식을 수정합니다.
- 영어·일본어 문서에 동일한 변경사항을 반영합니다.
- 변경 파일: 44개 (ko 18개, en 13개, ja 13개)

## 주요 변경 내용

- `**Label** :` → `**Label**:` bold 뒤 콜론 앞 공백 제거
- `**Role** **ARN**` → `**Role ARN**` 분리된 bold 병합
- `베이스로` / `ベースに` → `기반으로` / `基盤に` (YAML 형식 기반 표현 통일)
- 맞춤법·조사 오류 수정 (attribute을→를, 단일IP→단일 IP 등)
- 일부 문장 구조 개선 (단문 분리, 능동태 전환)

## Roundtrip 검증

- `normalize_bold` 스크립트의 `**(Title)**  :` 이중 공백 버그 수정
- reference-guide 문장 분리 (XHTML 2-paragraph 구조와 일치)

## Test plan

- [x] roundtrip 검증 통과 확인

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

Author: jk-kim0

src/content/en/administrator-manual/kubernetes/connection-management/cloud-providers.mdx

@@ -26,12 +26,12 @@ Administrator > Kubernetes > Connection Management > Cloud Providers
 2. Search by Cloud Provider name using the search box in the top left of the table
 3. Refresh the Cloud Provider list using the refresh button in the top right of the table
 4. The table provides the following column information:
-    1.  **Name**  : Cloud provider title
-    2.  **Cloud Provider**  : Connected platform
-    3.  **Region**  : Platform region
-    4.  **Replication Frequency** : Synchronization cycle setting
-    5.  **Created At**  : Cloud provider initial creation date and time
-    6.  **Updated At** : Cloud provider last modification date and time
+    1.  **Name**: Cloud provider title
+    2.  **Cloud Provider**: Connected platform
+    3.  **Region**: Platform region
+    4.  **Replication Frequency**: Synchronization cycle setting
+    5.  **Created At**: Cloud provider initial creation date and time
+    6.  **Updated At**: Cloud provider last modification date and time
 5. Click on each row to view cloud provider details
 
 

src/content/en/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws.mdx

@@ -69,8 +69,8 @@ Administrator > Kubernetes > Connection Management > Cloud Providers &g
   <figure data-layout="center" data-align="center">
   <img src="/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws/image-20240721-054206.png" alt="image-20240721-054206.png" width="510" />
   </figure>
-    1.  **Default Credentials**  : If the QueryPie server is installed in the same AWS account, you can assign an IAM role to the EC2 instance where QueryPie is installed to synchronize resources within the same AWS
-    2.  **Cross Account Role**  : You can create an IAM role to synchronize resources from other AWS accounts. Please create permissions for synchronization and assign policies according to the steps displayed on the screen
+    1.  **Default Credentials**: If the QueryPie server is installed in the same AWS account, you can assign an IAM role to the EC2 instance where QueryPie is installed to synchronize resources within the same AWS
+    2.  **Cross Account Role**: You can create an IAM role to synchronize resources from other AWS accounts. Please create permissions for synchronization and assign policies according to the steps displayed on the screen
 7. Use **Search Filter** to retrieve a list of specific resource types you want to synchronize
     1. Search Filter works the same way as AWS search. You can use values such as names and tags as filters, and conveniently enter search conditions and filters using the Enter key in the following order:
         1. Enter Key value and press Enter → Select search condition and press Enter → Enter Value value and press Enter
@@ -103,13 +103,13 @@ Administrator &gt; Kubernetes &gt; Connection Management &gt; Cloud Providers &g
     1. Please refer to **Dry Run/Synchronization Log Notation** below for notation definitions
     2. You can check the synchronization progress in the displayed Synchronization Log, and you can also check the synchronization history in Settings &gt; Systems &gt; Jobs menu
 4. Once a Cloud Provider is registered, some information cannot be changed
-    1.  **Name** : Can be changed
-    2.  **Cloud Provider** : Cannot be changed
-    3.  **Region** : Cannot be changed
-    4.  **Credential** : Cannot be changed
-    5.  **Role ARN** : Cannot be changed
-    6.  **Search Filter** : Can be changed
-    7.  **Replication Frequency** : Can be changed
+    1.  **Name**: Can be changed
+    2.  **Cloud Provider**: Cannot be changed
+    3.  **Region**: Cannot be changed
+    4.  **Credential**: Cannot be changed
+    5.  **Role ARN**: Cannot be changed
+    6.  **Search Filter**: Can be changed
+    7.  **Replication Frequency**: Can be changed
 
 
 ### Dry Run/Synchronization Log Notation

src/content/en/administrator-manual/kubernetes/connection-management/clusters.mdx

@@ -26,13 +26,13 @@ Administrator > Kubernetes > Connection Management > Clusters
 2. Search by cluster name using the search box in the top left of the table
 3. Refresh the cluster list using the refresh button in the top right of the table
 4. The table provides the following column information:
-    1.  **Name**  : Cluster name
-    2.  **Version**  : Cluster version
-    3.  **API URL**  : Cluster API URL
-    4.  **Cloud Provider**  : Connected platform (displayed as hyphen for manual clusters)
-    5.  **Tags**  : List of tags attached to the cluster
-    6.  **Created At**  : Cluster initial creation date and time
-    7.  **Updated At**  : Cluster last modification date and time
+    1.  **Name**: Cluster name
+    2.  **Version**: Cluster version
+    3.  **API URL**: Cluster API URL
+    4.  **Cloud Provider**: Connected platform (displayed as hyphen for manual clusters)
+    5.  **Tags**: List of tags attached to the cluster
+    6.  **Created At**: Cluster initial creation date and time
+    7.  **Updated At**: Cluster last modification date and time
 5. Click on each row to view cluster details
 
 

src/content/en/administrator-manual/kubernetes/connection-management/clusters/manually-registering-kubernetes-clusters.mdx

@@ -20,24 +20,24 @@ To manually register individual servers, you need to enter basic server informat
 
 1. Navigate to Administrator > Kubernetes > Connection Management > Clusters menu.
 2. Click the `+ Create Cluster` button in the top right.
-3.  **Information**  : Enter the following information for manual cluster registration
-    1.  **Name**  : Enter a name that can identify the cluster. (Required)
+3.  **Information**: Enter the following information for manual cluster registration
+    1.  **Name**: Enter a name that can identify the cluster. (Required)
         * This information cannot be modified in the future.
-    2.  **Version**  : Enter the cluster version. (Optional)
+    2.  **Version**: Enter the cluster version. (Optional)
         * This is an item that will be automatically filled through the credential authentication test procedure later.
-    3.  **API URL**  : Enter the API URL of the cluster that will receive the Kubernetes API.
+    3.  **API URL**: Enter the API URL of the cluster that will receive the Kubernetes API.
     4.
-    5.  **Credential**  : To grant access to the Kubernetes API server of the cluster, you need to obtain the service account token and CA certificate from the cluster. Please check the content in the blue information box for details.
-        1.  **Service Account Token**  : Enter the service account token value of the Kubernetes cluster that will be used when QueryPie Proxy makes user Kubernetes API calls.
-        2.  **Certificate Authority**  : Enter the CA certificate that QueryPie will use to verify the Kubernetes API server certificate.
-        3.  **Verify Credential**  : This button is activated when both the service account token and CA certificate are entered. Click the button to check if normal connection is possible. The result is displayed as follows based on the execution result:
-            * ✔️  **Verified**  : Indicates that the cluster connection was successful and the service account token and CA certificate were entered correctly.
-            * ❌  **Verification Failed**  : Indicates that the cluster connection failed, there may be an error in the service account token and CA certificate values, or network connection failed.
-    6.  **Logging Options**  : Select logging options for the cluster.
-        1.  **Request Audit**  : This is an option to enable logging for Kubernetes API call history for the cluster, and the default is `On`. When this function is switched to `Off`,
+    5.  **Credential**: To grant access to the Kubernetes API server of the cluster, you need to obtain the service account token and CA certificate from the cluster. Please check the content in the blue information box for details.
+        1.  **Service Account Token**: Enter the service account token value of the Kubernetes cluster that will be used when QueryPie Proxy makes user Kubernetes API calls.
+        2.  **Certificate Authority**: Enter the CA certificate that QueryPie will use to verify the Kubernetes API server certificate.
+        3.  **Verify Credential**: This button is activated when both the service account token and CA certificate are entered. Click the button to check if normal connection is possible. The result is displayed as follows based on the execution result:
+            * ✔️  **Verified**: Indicates that the cluster connection was successful and the service account token and CA certificate were entered correctly.
+            * ❌  **Verification Failed**: Indicates that the cluster connection failed, there may be an error in the service account token and CA certificate values, or network connection failed.
+    6.  **Logging Options**: Select logging options for the cluster.
+        1.  **Request Audit**: This is an option to enable logging for Kubernetes API call history for the cluster, and the default is `On`. When this function is switched to `Off`,
             1. Kubernetes API call history for the cluster will not be recorded.
             2. All Request Audit Types and Pod Session Recording below are bulk deactivated.
-        2.  **Request Audit Types**  : Administrators can select the target Verb to audit for the cluster. The default selects all of the following basic verbs.
+        2.  **Request Audit Types**: Administrators can select the target Verb to audit for the cluster. The default selects all of the following basic verbs.
             1. Verb types:
                 1. `get`
                 2. `list`
@@ -48,16 +48,16 @@ To manually register individual servers, you need to enter basic server informat
                 7. `delete`
                 8. `deletecollection`
             2. ✅ Select All : Audits all API calls.
-        3.  **Pod Session Recording**  : This is an option to enable recording for sessions opened by Pod exec commands within the cluster, and the default is `On`. This function is switched to `Off` if the following conditions are not met:
+        3.  **Pod Session Recording**: This is an option to enable recording for sessions opened by Pod exec commands within the cluster, and the default is `On`. This function is switched to `Off` if the following conditions are not met:
             1. Request Audit must be enabled to `On`.
             2. The following verbs must be selected in Request Audit Types:
                 1. `create`
                 2. `get`
-4.  **Tags**  : You can manually enter tags for individual clusters if necessary, and for clusters synchronized through Cloud Providers, synchronized tags are also displayed. (However, tags imported through synchronization cannot be deleted or modified.) Click the `+ Add Tag` button to add a new row and enter the desired tag value, and tags must be entered in key-value format.
-    1.  **Key**  : Enter a Key value that can distinguish the tag within 512 characters.
+4.  **Tags**: You can manually enter tags for individual clusters if necessary, and for clusters synchronized through Cloud Providers, synchronized tags are also displayed. (However, tags imported through synchronization cannot be deleted or modified.) Click the `+ Add Tag` button to add a new row and enter the desired tag value, and tags must be entered in key-value format.
+    1.  **Key**: Enter a Key value that can distinguish the tag within 512 characters.
         1. Key value must be entered as required, and already registered keys cannot be entered in duplicate.
         2. Duplicates are checked case-sensitively.
-    2.  **Value**  : Enter a Value value to be used for filtering within 256 characters.
+    2.  **Value**: Enter a Value value to be used for filtering within 256 characters.
 5. After going through the above process, click the final `Save` button to successfully register the cluster.
 
 

src/content/en/administrator-manual/kubernetes/k8s-access-control/access-control.mdx

@@ -33,11 +33,11 @@ Administrator > Kubernetes > K8s Access Control > Access Control > L
 2. You can search by user/group name using the search box at the top left of the table.
 3. You can refresh the user/group list using the refresh button at the top right of the table.
 4. The table displays the following information for each user/group:
-    1.  **User Type**  : User/group type
-    2.  **Provider**  : Represents the identity source of the user/group
-    3.  **Name**  : User/group name
-    4.  **Members**  : List of members belonging to the group
-    5.  **Roles**  : Number of granted Roles
+    1.  **User Type**: User/group type
+    2.  **Provider**: Represents the identity source of the user/group
+    3.  **Name**: User/group name
+    4.  **Members**: List of members belonging to the group
+    5.  **Roles**: Number of granted Roles
 5. Clicking a row in the Access Control list navigates to the detail page for the target user/group.
     1.   **Roles**
       <figure data-layout="center" data-align="center">
@@ -46,49 +46,49 @@ Administrator &gt; Kubernetes &gt; K8s Access Control &gt; Access Control &gt; L
         1. This is the default tab where you can view the list of granted Roles.
         2. You can search by Role name.
         3. The list displays the following information for each Role:
-            1.  **Name**  : Role name
-            2.  **Description**  : Role description
-            3.  **Expiration Date**  : Expiration date
-            4.  **Last Access At**  : Date and time of the last invocation of the Role
-            5.  **Granted At**  : Date and time when the Role was granted to the user/group
-            6.  **Granted By**  : Name of the administrator who granted the Role to the user/group
+            1.  **Name**: Role name
+            2.  **Description**: Role description
+            3.  **Expiration Date**: Expiration date
+            4.  **Last Access At**: Date and time of the last invocation of the Role
+            5.  **Granted At**: Date and time when the Role was granted to the user/group
+            6.  **Granted By**: Name of the administrator who granted the Role to the user/group
         4. Clicking each Role row displays the detailed information of the Role in a drawer format.
           <figure data-layout="center" data-align="center">
           <img src="/administrator-manual/kubernetes/k8s-access-control/access-control/image-20240721-065559.png" alt="image-20240721-065559.png" width="688" />
           </figure>
             1. Basic information is displayed at the top as follows:
-                1.  **Name**  : Role name
+                1.  **Name**: Role name
                     * (You can open the Role detail page link in a new window.)
-                2.  **Description**  : Role description
-                3.  **Granted At**  : Date and time when the Role was granted to the user/group
-                4.  **Granted By**  : Name of the administrator who granted the Role to the user/group
-                5.  **Last Access At**  : Date and time of the last invocation of the Role
-                6.  **Expiration Date**  : Expiration date
+                2.  **Description**: Role description
+                3.  **Granted At**: Date and time when the Role was granted to the user/group
+                4.  **Granted By**: Name of the administrator who granted the Role to the user/group
+                5.  **Last Access At**: Date and time of the last invocation of the Role
+                6.  **Expiration Date**: Expiration date
             2. The policies assigned to the Role are displayed as a list at the bottom.
-                1.  **Name**  : Policy name
+                1.  **Name**: Policy name
                     * (Provides a link to view the policy information.)
                       <figure data-layout="center" data-align="center">
                       <img src="/administrator-manual/kubernetes/k8s-access-control/access-control/image-20240721-065637.png" alt="image-20240721-065637.png" width="310" />
                       </figure>
-                2.  **Description**  : Policy description
-                3.  **Version**  : Policy version
-                4.  **Assigned At**  : Assignment date and time
-                5.  **Assigned By**  : Name of the administrator who assigned the policy
+                2.  **Description**: Policy description
+                3.  **Version**: Policy version
+                4.  **Assigned At**: Assignment date and time
+                5.  **Assigned By**: Name of the administrator who assigned the policy
     2.  **Clusters**
       <figure data-layout="center" data-align="center">
       <img src="/administrator-manual/kubernetes/k8s-access-control/access-control/image-20240721-065710.png" alt="image-20240721-065710.png" width="712" />
       </figure>
         1. Lists the Kubernetes clusters accessible through the granted Roles.
         2. You can search by Cluster name or Role name.
         3. The list displays the following information for each cluster:
-            1.  **Name**  : Cluster name
-            2.  **Version**  : Kubernetes version
-            3.  **API URL**  : Cluster API URL
-            4.  **Cloud Provider**  : Connected platform (displayed as a hyphen for manual clusters)
-            5.  **Tags**  : List of tags attached to the cluster
-            6.  **Role**  : List of related Roles
-            7.  **Created At**  : Cluster initial creation date and time
-            8.  **Updated At**  : Cluster last modification date and time
+            1.  **Name**: Cluster name
+            2.  **Version**: Kubernetes version
+            3.  **API URL**: Cluster API URL
+            4.  **Cloud Provider**: Connected platform (displayed as a hyphen for manual clusters)
+            5.  **Tags**: List of tags attached to the cluster
+            6.  **Role**: List of related Roles
+            7.  **Created At**: Cluster initial creation date and time
+            8.  **Updated At**: Cluster last modification date and time
 
 <Callout type="info">
 **How Granted Roles with an Expired Expiration Date Are Handled**

src/content/en/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles.mdx

@@ -35,11 +35,11 @@ Administrator > Kubernetes > K8s Access Control > Access Control
     1. You can search by Role name.
     2. Checkboxes for already assigned roles will be disabled.
     3. The list displays the following information for each policy:
-        1.  **Name**  : Role name
+        1.  **Name**: Role name
             * A new window link is provided to view the role information.
-        2.  **Description**  : Detailed description of the Role
-        3.  **Assigned Policies**  : Lists the assigned policies
-    4.  **Expiration Date**  : The expiration date must be specified.
+        2.  **Description**: Detailed description of the Role
+        3.  **Assigned Policies**: Lists the assigned policies
+    4.  **Expiration Date**: The expiration date must be specified.
         * By default, it is set to one year from the time of configuration, and can be set up to a maximum of one year.
 4. Click the `Grant` button to assign the checked Role.
 5. (Clicking the `Cancel` button closes the modal without any changes.)