mdx: FC bold-colon 서식 정규화를 ko/en/ja 문서에 적용합니다 (#964)

## Summary
- PR #963의 forward converter `close_sp` punctuation 체크 적용 결과를 ko/en/ja
문서에 반영합니다
- `**label** :` → `**label**:` (bold 뒤 불필요 공백 제거)
- `**"get"** , **"create"**` → `**"get"**, **"create"**` (bold 뒤 콤마 공백
제거)
- `**<u>...</u>** .` → `**<u>...</u>**.` (bold 뒤 마침표 공백 제거)
- ko 10개 파일, en 8개 파일, ja 8개 파일 (총 26개 파일, 48줄 변경)

## Test plan
- [ ] 변경된 MDX 파일이 정상적으로 렌더링되는지 확인

🤖 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/general/company-management/security.mdx

@@ -79,7 +79,7 @@ You can set timeout policies for web console and agents.
     * Timeout processing when there is no activity for the specified time
 *  **Agent Session Timeout** : Agent session timeout criteria (Default: 1,440 minutes)
     * Maintains agent app login for the specified time and processes logout when elapsed
-*  **User Inactivity Timeout (on agent)** : <br/> In addition to the Agent Session Timeout feature, the Agent monitors user mouse and keyboard input and forcibly terminates the session if there is no activity (keyboard key input, mouse click, mouse pointer movement, mouse wheel operation, mouse drag) beyond the specified time. In an idle state, even if a long-running query is being executed, if there is no mouse and keyboard movement, the session is terminated and logged out. User activity monitoring is performed every 30 seconds. The maximum idle expiration time cannot exceed the Agent Session Timeout.
+*  **User Inactivity Timeout (on agent)**: <br/> In addition to the Agent Session Timeout feature, the Agent monitors user mouse and keyboard input and forcibly terminates the session if there is no activity (keyboard key input, mouse click, mouse pointer movement, mouse wheel operation, mouse drag) beyond the specified time. In an idle state, even if a long-running query is being executed, if there is no mouse and keyboard movement, the session is terminated and logged out. User activity monitoring is performed every 30 seconds. The maximum idle expiration time cannot exceed the Agent Session Timeout.
 
 <Callout type="info">
 **Example of User Inactivity Timeout (on agent)**

src/content/en/administrator-manual/general/system/integrations/identity-providers.mdx

@@ -361,7 +361,7 @@ Okta details (1)
     * ACS Index : Enter a value between 0 and 2,147,483,647 (default is 0).
 
 <Callout type="info">
-**Assertion Consumer Service (ACS)** : A specific Endpoint (URL) located in the SP (Service provider) that receives SAML Assertions from the IdP, verifies them, and processes user login.
+**Assertion Consumer Service (ACS)**: A specific Endpoint (URL) located in the SP (Service provider) that receives SAML Assertions from the IdP, verifies them, and processes user login.
 
 <br/> **Why the Assertion Consumer Service Index is needed and its role**
 

src/content/en/administrator-manual/general/system/integrations/integrating-with-splunk.mdx

@@ -58,7 +58,7 @@ For reference, Splunk provides SC4S (Splunk connector for syslog) separately for
         3. To use HTTP instead of HTTPS, you must first configure Splunk's HEC option to not use SSL. When selecting HTTP, you must additionally enter the following field values:
             *  **HEC Host**  : Enter the hostname or IP address of the Splunk server.
             *  **HEC Token**  : Enter the Splunk HEC token value.
-    3.  **Destination Address (Hostname)** : Enter the IP address or hostname of the Splunk server or forwarder receiving syslog. For HTTP, HTTPS protocols, this changes to HEC Host input.
+    3.  **Destination Address (Hostname)**: Enter the IP address or hostname of the Splunk server or forwarder receiving syslog. For HTTP, HTTPS protocols, this changes to HEC Host input.
     4.  **Port**  : Enter the listening port of the syslog server. (TCP/UDP default 514)
         1. Splunk HEC port must be checked in Splunk settings first before entering.
         2. When selecting HTTP/HTTPS protocol in Splunk menu:

src/content/en/administrator-manual/general/system/integrations/integrating-with-syslog.mdx

@@ -39,7 +39,7 @@ Administrator > General > System > Integrations > Syslog > Config
 4. Enter the following information to create Destination information.
     1.  **Destination Name**  : Enter an appropriate name to identify the entity receiving syslog.
     2.  **Protocol**  : Protocols available in syslog are TCP (default) and UDP. UDP has packet length constraints and is vulnerable security-wise, so TCP usage is recommended.
-    3.  **Destination Address (Hostname)** : Enter the IP address or hostname of the syslog server receiving syslog.
+    3.  **Destination Address (Hostname)**: Enter the IP address or hostname of the syslog server receiving syslog.
     4.  **Port**  : Enter the port that the syslog server listens on. (default 514)
     5.  **Test Connection button**  : TCP can check communication status with the syslog server.
         * UDP cannot check communication status due to protocol characteristics, so the Test Connection button is disabled.

src/content/en/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-tips-guide.mdx

@@ -39,7 +39,7 @@ The following information is displayed to guide you when writing Policy code:
 | `conditions`<br/>`resourceTags`                            |  **(Optional) Add Tag Conditions**             | Filter target QueryPie-managed resources via tags in QueryPie. (e.g., "region": "ap-northeast-*")                                                                                                                                                                                                     |
 | `conditions`<br/>`userAttributes`                          |  **(Optional) Add User Attribute Conditions**  | Specify user attributes for fine-grained policy enforcement. Only users matching specified attributes can utilize this policy. (e.g., "department": "DevOps")                                                                                                                                         |
 | `conditions`<br/>`ipAddresses`                             |  **(Optional) List IP Addresses**              | List IP address ranges to utilize this policy. Input either in a single IP address or CIDR format. (e.g., ["10.0.0.0/24", "10.10.10.10"])                                                                                                                                                             |
-| `actions`<br/>`resources``"pods/exec"`                     | **Specify Verb "get"** , **"create"**        | "pods/exec" resource requires the verbs "get", "create" for users to call its action. Also, authorization to "get" & "list" "pods" is required.                                                                                                                                                       |
+| `actions`<br/>`resources``"pods/exec"`                     | **Specify Verb "get"**, **"create"**         | "pods/exec" resource requires the verbs "get", "create" for users to call its action. Also, authorization to "get" & "list" "pods" is required.                                                                                                                                                       |
 | `actions`<br/>`resources``"pods/log"`                      |  **Specify Verb "get"**                        | "pods/log" resource requires the verb "get" for users to call its action. Also, authorization to "get" & "list" "pods" is required.                                                                                                                                                                   |
-| `actions`<br/>`resources``"pods/portforward"`              | **Specify Verb "get"** , **"create"**        | "pods/portforward" resource requires the verbs "get", "create" for users to call its action. Also, authorization to "get" & "list" "pods" is required.                                                                                                                                                |
+| `actions`<br/>`resources``"pods/portforward"`              | **Specify Verb "get"**, **"create"**         | "pods/portforward" resource requires the verbs "get", "create" for users to call its action. Also, authorization to "get" & "list" "pods" is required.                                                                                                                                                |
 | `actions`<br/>`verbs`without `"get"`, `"list"`, `"watch"`  |  **Add Verbs "get" and/or "list"**             | It is a common practice to use verbs "get" and/or "list" for view before performing an Edit operation to ensure consistency and accuracy.                                                                                                                                                             |

src/content/en/installation/prerequisites/linux-distribution-and-docker-podman-support-status.mdx

@@ -235,7 +235,7 @@ On the other hand, Podman is not provided in the default repository, and even th
 Compose can deploy and update Docker Compose plugins (v2) together, enabling stable management of multi-container services on a single host.
 
 * Suitable for using Docker and Docker Compose combination.
-*  **<u>Podman is not supported</u>** .
+*  **<u>Podman is not supported</u>**.
 
 #### Amazon Linux 2023 (Released March 2023)
 

src/content/en/user-manual/workflow/requesting-ip-registration.mdx

@@ -91,16 +91,16 @@ On this page, you can request IP registration by following the procedures below.
 
 1.  **Select Approval Rule** : Select the approval rule to use from the dropdown list.
 2.  **Enter IP Addresses** : Enter the IP addresses for which you want to allow access, separated by commas (`,`). (Maximum 20)
-3.  **Submit Request** : Submit the request by clicking the `Submit` button.
+3.  **Submit Request**: Submit the request by clicking the `Submit` button.
 
 
 #### Auto-filled Items
 
 When submitting a request from the login block page, the following items are automatically generated and filled by the system for user convenience.
 
-*  **Title** : `IP Registration Request from {User Name} ({Login ID})`
-*  **Reason for Request** : `I, {User Name}, am requesting IP registration because I am currently unable to access the system with my existing IP address. Please allow access from the IP address provided.`
-*  **Due Date** : Automatically set to one year from the request date.
+*  **Title**: `IP Registration Request from {User Name} ({Login ID})`
+*  **Reason for Request**: `I, {User Name}, am requesting IP registration because I am currently unable to access the system with my existing IP address. Please allow access from the IP address provided.`
+*  **Due Date**: Automatically set to one year from the request date.
 
 
 #### After Request Submission

src/content/en/user-manual/workflow/requesting-server-privilege.mdx

@@ -126,7 +126,7 @@ Therefore, the field for entering or selecting Commands is not displayed on the
 *  **Start Trigger**  : Select the permission grant start condition.
     * Access to the Server : After Server Privilege is applied, it counts time from when the applied user starts server access.
     * Grant : It counts the Server Privilege usage time from the Server Privilege grant time. When the Request is approved, QueryPie automatically grants Server Privilege.
-*  **Duration(Minutes)** : Set the Server Privilege application time. You can input time in minutes. The start time varies depending on the Privilege Start Trigger.
+*  **Duration(Minutes)**: Set the Server Privilege application time. You can input time in minutes. The start time varies depending on the Privilege Start Trigger.
 
 ##### When Require Minute-Based Requests is Off
 

src/content/ja/administrator-manual/general/company-management/security.mdx

@@ -79,7 +79,7 @@ QueryPieアカウントのパスワードポリシーを設定できます。
     * 指定された時間活動がない場合タイムアウト処理
 *  **Agent Session Timeout** : エージェントセッションタイムアウト基準 (Default : 1,440分)
     * 指定された時間エージェントアプリログインを維持し、経過時ログアウト処理
-*  **User Inactivity Timeout (on agent)** :  <br/> Agent Session Timeout機能に追加でAgentがユーザーのマウス、キーボード入力をモニタリングし、指定された時間を超過して行動(キーボードのキー入力、マウスクリック、マウスポインター移動、マウスホイール操作、マウスドラッグ)がない場合セッションを強制終了します。アイドル状態の場合、長時間クエリを実行していてもマウスおよびキーボードの動きがないと無条件にセッションが終了されログアウト処理されます。ユーザー行動監視は30秒ごとに実行します。最大アイドル期限時間がAgent Session Timeoutを超過できません。
+*  **User Inactivity Timeout (on agent)**:  <br/> Agent Session Timeout機能に追加でAgentがユーザーのマウス、キーボード入力をモニタリングし、指定された時間を超過して行動(キーボードのキー入力、マウスクリック、マウスポインター移動、マウスホイール操作、マウスドラッグ)がない場合セッションを強制終了します。アイドル状態の場合、長時間クエリを実行していてもマウスおよびキーボードの動きがないと無条件にセッションが終了されログアウト処理されます。ユーザー行動監視は30秒ごとに実行します。最大アイドル期限時間がAgent Session Timeoutを超過できません。
 
 <Callout type="info">
 **User Inactivity Timeout (on agent)設定例**

src/content/ja/administrator-manual/general/system/integrations/integrating-with-email.mdx

@@ -33,7 +33,7 @@ Email送信にはSMTPサーバーが必要で、QueryPieではSMTPサーバー
     2.  **Host**  : SMTPサーバーのhostname（FQDN）を入力します。
     3.  **Secure**  : 暗号化送信方式を選択します。TLS、STARTTLSの中から選択できます。デフォルト値はTLSです。<br/>STARTTLSはSMTP ServerがTLSを使用できない場合平文を使用します。
     4.  **Port**  : SMTPサーバーが使用するポート番号を入力します。
-    5.  **Timeout (milliseconds)** : SMTPの応答を待機する閾値を入力します。デフォルト値は60000です。必ず必要な場合でなければ可能な限りこの値を修正しないようにします。
+    5.  **Timeout (milliseconds)**: SMTPの応答を待機する閾値を入力します。デフォルト値は60000です。必ず必要な場合でなければ可能な限りこの値を修正しないようにします。
     6.  **Sender Email Address**  : メール送信者のメールアドレスを入力します。
     7.  **Sender Name**  : メール送信者の名前で表示される内容を入力します。
     8.  **Support Email Address (Reply-to)**  : クエリパイでSMTPサーバーに送信するメールはすべて送信専用メールです。Sender Email Addressに入力した送信専用メールアドレスはユーザーの返信メールを受信できないため、場合によってメール受信者が技術サポートをリクエストする必要がある時メールを受信するアドレスを提供する必要があります。<br/>10.2.2基準パスワード初期化emailテンプレート、2次認証用認証コードメールテンプレートでここで指定したsupport email addressを使用するようになっています。