fix(mdx): Inline Code 내 <, > 문자가 올바르게 표시되도록 MDX 파일 수정

src/content/en/administrator-manual/audit/reports/audit-log-export.mdx

@@ -121,19 +121,19 @@ When extracting logs by selecting the current date, since data is accumulated in
 
 - Number Type
 
-Supported expressions: `&gt;`, `&lt;`, `&lt;=`, `&gt;=`, `==`, `!=`<br/>Example: `x &gt; `10``, `x == `10``
+Supported expressions: `>`, `<`, `<=`, `>=`, `==`, `!=`<br/>Example: `x > `10``, `x == `10``
 
 - String Type
 
 Supported expressions: `== (equals)`, `!= (not equals)`, `contains`<br/>Example: `x == 'abc'`, `x != 'abc'`, `contains(x, 'ab')`
 
 - Boolean Type
 
-Supported expressions: `== (equals)`, `!= (not equals)`, `&& (and)`, `|| (or)`<br/>Example: `x == `true``,`x && y`, `(x &gt; `0`) && (y == `0`)`
+Supported expressions: `== (equals)`, `!= (not equals)`, `&& (and)`, `|| (or)`<br/>Example: `x == `true``,`x && y`, `(x > `0`) && (y == `0`)`
 
 - Array Type
 
-Example: `x[? @ == 'value']`, `list[? @ &gt; `10`]`
+Example: `x[? @ == 'value']`, `list[? @ > `10`]`
 
 
 (3) You can use the following characters to use multiple conditions together:

src/content/en/administrator-manual/databases/connection-management/db-connections.mdx

@@ -186,7 +186,7 @@ DB Account items are displayed differently depending on the Secret Engine type s
 * When `Secret Engine` = K/V setting, Username / Password input fields are displayed on the connection information page.
     * Enter the Vault Path in the Username / Password fields.
     * Path can be entered in the format `prod_db/data/mysql?username`.
-    * Based on the example, the actual path in Vault is when the key `username` exists in `prod_db > mysql`.
+    * Based on the example, the actual path in Vault is when the key `username` exists in `prod_db > mysql`.
     * The `/data` path in the middle must be added.
 * When `Secret Engine` = Database setting, Account input field is displayed on the connection information page.
     * Enter the Vault Path in the Account field.

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

@@ -92,7 +92,7 @@ It is a value managed by the system and does not need to be modified.
 </tr>
 <tr>
 <td>
-`spec:`<br/> `&lt;effect&gt;`
+`spec:`<br/> `<effect>`
 </td>
 <td>
 -

src/content/en/administrator-manual/web-apps/wac-quickstart/1027-wac-role-policy-guide.mdx

@@ -92,7 +92,7 @@ System-managed value, no modification needed
 </tr>
 <tr>
 <td>
-`spec:`<br/> `&lt;effect&gt;`
+`spec:`<br/> `<effect>`
 </td>
 <td>
 -

src/content/en/administrator-manual/web-apps/wac-quickstart/1028-wac-rbac-guide.mdx

@@ -122,7 +122,7 @@ System-managed value, no modification needed
 </tr>
 <tr>
 <td>
-`spec:`<br/> `&lt;effect&gt;`
+`spec:`<br/> `<effect>`
 </td>
 <td>
 -

src/content/en/installation/installation/comparison-of-setupsh-and-setupv2sh.mdx

@@ -25,12 +25,12 @@ This document examines how these two installation programs work, their features,
 * Installs Container Engine and Compose Tool if not found.
     * Container Engine: Docker or Podman
     * Compose Tool: Docker Compose
-* Installs package.tar.gz for Compose at the `./querypie/<version>` path.
+* Installs package.tar.gz for Compose at the `./querypie/<version>` path.
 * Checks SELinux settings and performs `chcon` command for Container Volume Mount.
 * Automatically fills in setting values in the environment variable configuration file `.env`.
 * Downloads Container Images.
 * Performs QueryPie MySQL Migration and runs QueryPie App Container.
-* Creates a Symbolic Link `./querypie/current` pointing to `./querypie/&lt;version&gt;` to indicate the currently running version.
+* Creates a Symbolic Link `./querypie/current` pointing to `./querypie/<version>` to indicate the currently running version.
 
 #### Additional Features of setup.v2.sh for Upgrade, Deletion, etc.
 
@@ -49,7 +49,7 @@ setup.v2.sh provides other major features in addition to product installation.
 | Image Registry    | `harbor.chequer.io/querypie/`                              | `docker.io/querypie/`                              |
 | Environment Variable Configuration File         | `compose-env`                                              | `.env`                                             |
 | Compose as Plugin | Not supported<br/>Uses `docker-compose` command                            | Supported<br/>Uses `docker compose` or `podman compose` command |
-| MySQL Data Dir    | `./querypie/&lt;version&gt;/mysql/`                        | `./querypie/mysql/`                                |
+| MySQL Data Dir    | `./querypie/<version>/mysql/`                              | `./querypie/mysql/`                                |
 | Application Log   | `/var/log/querypie/` - 10.2.x<br/>`./querypie/log/` - 11.x | `./querypie/log/`                                  |
 | Symlink for Running Version  | (None)                                                       | `./querypie/current`                               |
 

src/content/en/installation/installation/installation-guide-setupv2sh.mdx

@@ -221,7 +221,7 @@ Values set in .env such as DB_PASSWORD, REDIS_PASSWORD, KEY_ENCRYPTION_KEY must
 Please be careful not to expose these values to others.
 </Callout>
 
-Replace the `&lt;customer-proxy-address&gt;` part below with your customer's Proxy access IP or domain and execute the query.
+Replace the `<customer-proxy-address>` part below with your customer's Proxy access IP or domain and execute the query.
 
 <Callout type="important">
 This address should not have a Scheme such as `http` or `https` attached.
@@ -246,7 +246,7 @@ When you attempt to log in from User Agent, after authentication through a web b
 
 Connect to QueryPie Database and register the address for KAC Proxy access.
 
-Replace the `&lt;customer-proxy-fqdn&gt;` part below with your customer's Proxy access IP or domain and execute the query.
+Replace the `<customer-proxy-fqdn>` part below with your customer's Proxy access IP or domain and execute the query.
 
 As a special note, unlike DAC/SAC settings, you can freely enter Schemes such as `http` or `https`.
 

src/content/en/installation/installation/installation-guide-simple-configuration.mdx

@@ -118,7 +118,7 @@ Login Succeeded
 
 ### compose-env Configuration
 
-When you run the `./setup.sh` script, it creates configuration files such as `docker-compose.yml` and `compose-env` in the `querypie/<version>/` directory.
+When you run the `./setup.sh` script, it creates configuration files such as `docker-compose.yml` and `compose-env` in the `querypie/<version>/` directory.
 Move into this directory and edit the configuration file named `compose-env`.
 
 For descriptions of each environment variable, please refer to the following document: [Container Environment Variables](../container-environment-variables)
@@ -336,7 +336,7 @@ Values set in compose-env such as DB_PASSWORD, REDIS_PASSWORD, KEY_ENCRYPTION_KE
 Please be careful not to expose these values to others.
 </Callout>
 
-Replace the `&lt;customer-proxy-address&gt;` part below with your customer's Proxy access IP or domain and execute the query.
+Replace the `<customer-proxy-address>` part below with your customer's Proxy access IP or domain and execute the query.
 
 <Callout type="important">
 This address should not have a Scheme such as `http` or `https` attached.
@@ -361,7 +361,7 @@ When you attempt to log in from User Agent, after authentication through a web b
 
 Connect to QueryPie Database and register the address for KAC Proxy access.
 
-Replace the `&lt;customer-proxy-fqdn&gt;` part below with your customer's Proxy access IP or domain and execute the query.
+Replace the `<customer-proxy-fqdn>` part below with your customer's Proxy access IP or domain and execute the query.
 
 As a special note, unlike DAC/SAC settings, you can freely enter Schemes such as `http` or `https`.
 

src/content/en/installation/prerequisites/configuring-rootless-mode-with-podman.mdx

@@ -106,7 +106,7 @@ Created symlink /home/ec2-user/.config/systemd/user/default.target.wants/podman-
 
 When Using Separately Configured MySQL
 
-If you use a separately configured MySQL instead of running MySQL on one Linux server using the default `./querypie/<version>/compose.yml`, you can change the systemd service operation scope.
+If you use a separately configured MySQL instead of running MySQL on one Linux server using the default `./querypie/<version>/compose.yml`, you can change the systemd service operation scope.
 
 You just need to not activate `podman-querypie-database.service`.
 You can turn off running systemd services with the following command.

src/content/en/user-manual/database-access-control/setting-default-privilege.mdx

@@ -30,7 +30,7 @@ QueryPie Web > Database Access Control > Databases > Privileges > De
 </figcaption>
 </figure>
 
-1. Click the `Edit` button or `&gt; Go to Settings` link on the right of Privileges.
+1. Click the `Edit` button or `> Go to Settings` link on the right of Privileges.
 2. In the Privilege section, select the Privilege to use as the default value among the granted permissions.
 3. Click the Save button to complete the Default Privilege setting.
 

src/content/en/user-manual/multi-agent.mdx

@@ -246,7 +246,7 @@ When you don't have the necessary account permissions to connect to a server, yo
 
 <Callout type="info">
 **Notes**
-* If the QueryPie administrator disables `Server Privilege Request` in the `Admin &gt; General &gt; Workflow Configurations` setting, the `Request Server Privilege` button in the agent is also disabled.
+* If the QueryPie administrator disables `Server Privilege Request` in the `Admin > General > Workflow Configurations` setting, the `Request Server Privilege` button in the agent is also disabled.
 </Callout>
 
 

src/content/ja/administrator-manual/audit/reports/audit-log-export.mdx

@@ -121,19 +121,19 @@ Administrator > Audit > General > Audit Log Export > Create New Task
 
 - Number Type
 
-サポートする表現式: `&gt;`, `&lt;`, `&lt;=`, `&gt;=`, `==`, `!=`<br/>例: `x &gt; `10``, `x == `10``
+サポートする表現式: `>`, `<`, `<=`, `>=`, `==`, `!=`<br/>例: `x > `10``, `x == `10``
 
 - String Type
 
 サポートする表現式: `== (equals)`, `!= (not equals)`, `contains`<br/>例: `x == 'abc'`, `x != 'abc'`, `contains(x, 'ab')`
 
 - Boolean Type
 
-サポートする表現式: `== (equals)`, `!= (not equals)`, `&& (and)`, `|| (or)`<br/>例: `x == `true``,`x && y`, `(x &gt; `0`) && (y == `0`)`
+サポートする表現式: `== (equals)`, `!= (not equals)`, `&& (and)`, `|| (or)`<br/>例: `x == `true``,`x && y`, `(x > `0`) && (y == `0`)`
 
 - Array Type
 
-例: `x[? @ == 'value']`, `list[? @ &gt; `10`]`
+例: `x[? @ == 'value']`, `list[? @ > `10`]`
 
 
 (3) 複数の条件を一緒に使用するために以下の文字を活用できます。

src/content/ja/administrator-manual/databases/connection-management/db-connections.mdx

@@ -186,7 +186,7 @@ Secret Store設定に保存されたSecret Engineタイプに 따라DB Account
 * `Secret Engine` = K/V設定時、コネクション情報ページでUsername / Password入力項目が表示されます。
     * Username / Password項目にVaultのPathを入力します。
     * Pathの形態は`prod_db/data/mysql?username`形態で入力できます。
-    * 例基準実際にVault内の経路は`prod_db > mysql`のkeyが`username`の場合です。
+    * 例基準実際にVault内の経路は`prod_db > mysql`のkeyが`username`の場合です。
     * 中間の`/data`経路を追加しなければなりません。
 * `Secret Engine` = Database設定時、コネクション情報ページでAccount入力項目が表示されます。
     * Account項目にVaultのPathを入力します。

src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-yaml-code-syntax-guide.mdx

@@ -92,7 +92,7 @@ O
 </tr>
 <tr>
 <td>
-`spec:`<br/> `&lt;effect&gt;`
+`spec:`<br/> `<effect>`
 </td>
 <td>
 -

src/content/ja/administrator-manual/web-apps/wac-quickstart/1027-wac-role-policy-guide.mdx

@@ -92,7 +92,7 @@ WACのポリシーはYAML形式で記述され、その基本構造は以下の
 </tr>
 <tr>
 <td>
-`spec:`<br/>  `&lt;effect&gt;`
+`spec:`<br/>  `<effect>`
 </td>
 <td>
 -

src/content/ja/administrator-manual/web-apps/wac-quickstart/1028-wac-rbac-guide.mdx

@@ -122,7 +122,7 @@ spec:
 </tr>
 <tr>
 <td>
-`spec:`<br/>  `&lt;effect&gt;`
+`spec:`<br/>  `<effect>`
 </td>
 <td>
 -

src/content/ja/installation/installation/comparison-of-setupsh-and-setupv2sh.mdx

@@ -25,12 +25,12 @@ setup.v2.shはQueryPie Community Editionリリースとともに提供されるQ
 * Container Engine、Compose Toolが発見されない場合、これらをインストールします。
     * Container Engine：DockerまたはPodman
     * Compose Tool: Docker Compose
-* `./querypie/<version>`経路にComposeのためのpackage.tar.gzをインストールします。
+* `./querypie/<version>`経路にComposeのためのpackage.tar.gzをインストールします。
 * SELinux設定を点検し、Container Volume Mountのための`chcon`コマンドを実行します。
 * 環境変数設定ファイル`.env`の設定値を自動的に埋めます。
 * Container Imageをダウンロードします。
 * QueryPie MySQLのMigrationを実行し、QueryPie App Containerを実行します。
-* `./querypie/current`というSymbolic Linkを`./querypie/&lt;version&gt;`に接続して、現在動作中のバージョンを明示します。
+* `./querypie/current`というSymbolic Linkを`./querypie/<version>`に接続して、現在動作中のバージョンを明示します。
 
 #### setup.v2.shのアップグレード、削除など追加機能
 
@@ -49,7 +49,7 @@ setup.v2.shは製品のインストール以外にも他の主要機能を提供
 | Image Registry    | `harbor.chequer.io/querypie/`                              | `docker.io/querypie/`                              |
 | 環境変数設定ファイル         | `compose-env`                                              | `.env`                                             |
 | Compose as Plugin | 未サポート<br/>`docker-compose`コマンドを使用                            | サポート<br/>`docker compose`または`podman compose`コマンドを使用 |
-| MySQL Data Dir    | `./querypie/&lt;version&gt;/mysql/`                        | `./querypie/mysql/`                                |
+| MySQL Data Dir    | `./querypie/<version>/mysql/`                              | `./querypie/mysql/`                                |
 | Application Log   | `/var/log/querypie/` - 10.2.x<br/>`./querypie/log/` - 11.x | `./querypie/log/`                                  |
 | 動作中バージョンのSymlink  | （なし）                                                       | `./querypie/current`                               |
 

src/content/ja/installation/installation/installation-guide-setupv2sh.mdx

@@ -221,7 +221,7 @@ Database接続設定過程でQueryPie MySQLのHostname、Username、Passwordが
 他の人にこの値を露出しないよう注意してください。
 </Callout>
 
-以下`&lt;customer-proxy-address&gt;`部分を顧客社のProxy接続IPまたはドメインに置き換えてクエリを実行します。
+以下`<customer-proxy-address>`部分を顧客社のProxy接続IPまたはドメインに置き換えてクエリを実行します。
 
 <Callout type="important">
 該当アドレスは`http` `https`のようなSchemeを付けてはいけません。
@@ -246,7 +246,7 @@ User Agentからログインを試みると、ウェブブラウザを通じて
 
 QueryPie Databaseに接続して、KACのProxy接続のためのアドレスを登録します。
 
-以下`&lt;customer-proxy-fqdn&gt;`部分を顧客社のProxy接続IPまたはドメインに置き換えてクエリを実行します。
+以下`<customer-proxy-fqdn>`部分を顧客社のProxy接続IPまたはドメインに置き換えてクエリを実行します。
 
 特記事項としてDAC/SAC設定とは異なり`http` `https`のようなSchemeを自由に入力可能です。
 

src/content/ja/installation/installation/installation-guide-simple-configuration.mdx

@@ -118,7 +118,7 @@ Login Succeeded
 
 ### compose-env設定
 
-`./setup.sh`スクリプトを実行すると、`querypie/<version>/`ディレクトリ内に`docker-compose.yml`、`compose-env`など設定ファイルを生成します。
+`./setup.sh`スクリプトを実行すると、`querypie/<version>/`ディレクトリ内に`docker-compose.yml`、`compose-env`など設定ファイルを生成します。
 このディレクトリ内に移動して、`compose-env`という名前の設定ファイルを編集します。
 
 各環境変数に関する説明は次の文書を参照してください：[コンテナ環境変数案内](../container-environment-variables)
@@ -336,7 +336,7 @@ compose-envに設定された値のうちDB_PASSWORD、REDIS_PASSWORD、KEY_ENCR
 他の人にこの値を露出しないよう注意してください。
 </Callout>
 
-以下`&lt;customer-proxy-address&gt;`部分を顧客社のProxy接続IPまたはドメインに置き換えてクエリを実行します。
+以下`<customer-proxy-address>`部分を顧客社のProxy接続IPまたはドメインに置き換えてクエリを実行します。
 
 <Callout type="important">
 該当アドレスは`http` `https`のようなSchemeを付けてはいけません。
@@ -361,7 +361,7 @@ User Agentからログインを試みると、ウェブブラウザを通じて
 
 QueryPie Databaseに接続して、KACのProxy接続のためのアドレスを登録します。
 
-以下`&lt;customer-proxy-fqdn&gt;`部分を顧客社のProxy接続IPまたはドメインに置き換えてクエリを実行します。
+以下`<customer-proxy-fqdn>`部分を顧客社のProxy接続IPまたはドメインに置き換えてクエリを実行します。
 
 特記事項としてDAC/SAC設定とは異なり`http` `https`のようなSchemeを自由に入力可能です。
 

src/content/ja/installation/prerequisites/configuring-rootless-mode-with-podman.mdx

@@ -106,7 +106,7 @@ Created symlink /home/ec2-user/.config/systemd/user/default.target.wants/podman-
 
 別途構成されたMySQLを使用する場合
 
-基本提供される`./querypie/<version>/compose.yml`を利用して、1つのLinuxサーバでMySQLを実行せず、別途構成されたMySQLを使用する場合、systemd service動作範囲を変更すればよいです。
+基本提供される`./querypie/<version>/compose.yml`を利用して、1つのLinuxサーバでMySQLを実行せず、別途構成されたMySQLを使用する場合、systemd service動作範囲を変更すればよいです。
 
 `podman-querypie-database.service`を動作させなければよいです。
 動作中のsystemd serviceを次のコマンドでオフにできます。

src/content/ja/user-manual/database-access-control/setting-default-privilege.mdx

@@ -30,7 +30,7 @@ QueryPie Web > Database Access Control > Databases > Privileges > De
 </figcaption>
 </figure>
 
-1. Privileges右側の`Edit`ボタンまたは`&gt; Go to Settings`リンクをクリックします。
+1. Privileges右側の`Edit`ボタンまたは`> Go to Settings`リンクをクリックします。
 2. Privilege項目で付与された権限の中から基本値で使用するPrivilegeを選択します。
 3. SaveボタンをクリックしてDefault Privilege設定を完了します。
 

src/content/ja/user-manual/multi-agent.mdx

@@ -246,7 +246,7 @@ Multi-Agent > Setting > Kubernetes
 
 <Callout type="info">
 **注意事項**
-* QueryPie管理者が`Admin &gt; General &gt; Workflow Configurations`設定で`Server Privilege Request`を非活性化した場合、エージェントの`Request Server Privilege`ボタンも非活性化されます。
+* QueryPie管理者が`Admin > General > Workflow Configurations`設定で`Server Privilege Request`を非活性化した場合、エージェントの`Request Server Privilege`ボタンも非活性化されます。
 </Callout>
 
 

src/content/ko/administrator-manual/audit/reports/audit-log-export.mdx

@@ -121,19 +121,19 @@ Administrator > Audit > General > Audit Log Export > Create New Task
 
 - Number Type
 
-지원하는 표현식 : `&gt;`, `&lt;`, `&lt;=`, `&gt;=`, `==`, `!=`<br/>예 : `x &gt; `10``, `x == `10``
+지원하는 표현식 : `>`, `<`, `<=`, `>=`, `==`, `!=`<br/>예 : `x > `10``, `x == `10``
 
 - String Type
 
 지원하는 표현식 : `== (equals)`, `!= (not equals)`, `contains`<br/>예 : `x == 'abc'`, `x != 'abc'`, `contains(x, 'ab')`
 
 - Boolean Type
 
-지원하는 표현식 : `== (equals)`, `!= (not equals)`, `&& (and)`, `|| (or)`<br/>예 : `x == `true``,`x && y`, `(x &gt; `0`) && (y == `0`)`
+지원하는 표현식 : `== (equals)`, `!= (not equals)`, `&& (and)`, `|| (or)`<br/>예 : `x == `true``,`x && y`, `(x > `0`) && (y == `0`)`
 
 - Array Type
 
-예 : `x[? @ == 'value']`, `list[? @ &gt; `10`]`
+예 : `x[? @ == 'value']`, `list[? @ > `10`]`
 
 
 (3) 여러 조건을 함께 사용하기 위해 아래의 문자를 활용할 수 있습니다.

src/content/ko/administrator-manual/databases/connection-management/db-connections.mdx

@@ -186,7 +186,7 @@ Secret Store 설정에 저장된 Secret Engine 타입에 따라 DB Account 항
 * `Secret Engine` = K/V 설정시, 커넥션 정보 페이지에서 Username / Password 입력 항목이 표시됩니다.
     * Username / Password 항목에 Vault 의 Path 를 입력합니다.
     * Path 의 형태는 `prod_db/data/mysql?username` 형태로 입력할 수 있습니다.
-    * 예시 기준 실제로 Vault 내의 경로는 `prod_db > mysql` 의 key 가 `username` 인 경우입니다.
+    * 예시 기준 실제로 Vault 내의 경로는 `prod_db > mysql` 의 key 가 `username` 인 경우입니다.
     * 중간의 `/data` 경로를 추가해야합니다.
 * `Secret Engine` = Database 설정시, 커넥션 정보 페이지에서 Account 입력 항목이 표시됩니다.
     * Account 항목에 Vault 의 Path 를 입력합니다.

src/content/ko/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-yaml-code-syntax-guide.mdx

@@ -92,7 +92,7 @@ O
 </tr>
 <tr>
 <td>
-`spec:`<br/>  `&lt;effect&gt;`
+`spec:`<br/>  `<effect>`
 </td>
 <td>
 -