AUTO: Sync ScalarDB docs in English to docs site repo (#1732)

Co-authored-by: josh-wong <[email protected]>

Author: github-actions[bot]

versioned_docs/version-3.16/scalardb-analytics/deploy-scalardb-analytics-server.mdx

@@ -13,11 +13,11 @@ import HelmCommandUsage from '/src/components/en-us/_helm-command-usage.mdx';
 
 This document explains how to deploy a ScalarDB Analytics server in your local or production environment.
 
-## Step 1. Decide on the billing method for ScalarDB Analytics
+## Step 1. Select a billing plan for ScalarDB Analytics
 
 You can get the ScalarDB Analytics server in several ways:
 
-<Tabs groupId="billing-method" queryString>
+<Tabs groupId="billing-plan" queryString>
   <TabItem value="pay-as-you-go" label="Pay as you go" default>
     You can use ScalarDB Analytics in a pay-as-you-go plan. In this case, you will pay the license fee based on your query usage.
     <Tabs groupId="cloud" queryString>
@@ -46,11 +46,11 @@ After subscribing, you'll have permission to pull the container image of the Sca
       </TabItem>
     </Tabs>
   </TabItem>
-  <TabItem value="fixed-price-byil" label="Fixed price (bring your own license)">
-    You can use ScalarDB Analytics in a fixed-price method. In this case, you will pay the fixed license fee based on your contract, with an upper limit on the queries you can run.
+  <TabItem value="fixed-price-byol" label="Fixed price (bring your own license)">
+    You can use ScalarDB Analytics at a fixed price. In this case, you will pay the fixed license fee based on your contract, with an upper limit on the queries you can run.
     <Tabs groupId="cloud" queryString>
       <TabItem value="any-supported-kubernetes" label="Any supported Kubernetes platform" default>
-        You can use ScalarDB Analytics in the fixed-price method on any supported Kubernetes platforms. You can see the supported Kubernetes platforms in [Requirements](../requirements.mdx#kubernetes).
+        You can use ScalarDB Analytics at a fixed price on any supported Kubernetes platforms. You can see the supported Kubernetes platforms in [Requirements](../requirements.mdx#kubernetes).
         <Tabs groupId="offering" queryString>
           <TabItem value="container" label="Container offer" default>
             <WarningLicenseKeyContact product="ScalarDB Analytics server" />
@@ -76,10 +76,10 @@ You will specify this container registry in a later step, so keep note of it.
 
 Deploy a cluster on your preferred Kubernetes platform based on the following requirements and checkpoints:
 
-1. Decide which Kubernetes platform to use based on the billing method and purpose.
+1. Decide which Kubernetes platform to use based on the billing plan and purpose.
 
-   - If you chose **Pay as you go (container offer - AWS Marketplace)** in [Step 1. Decide on the billing method for ScalarDB Analytics](#step-1-decide-on-the-billing-method-for-scalardb-analytics), you need to deploy Amazon Elastic Kubernetes Service (EKS) in the supported regions. The supported regions will be referred to in a later step.
-   - If you chose **Fixed price w/bring your own license (container offer - any supported Kubernetes platform)** in [Step 1. Decide on the billing method for ScalarDB Analytics](#step-1-decide-on-the-billing-method-for-scalardb-analytics), you can use any of the supported Kubernetes platforms.
+   - If you chose **Pay as you go (container offer - AWS Marketplace)** in [Step 1. Select a billing plan for ScalarDB Analytics](#step-1-select-a-billing-plan-for-scalardb-analytics), you need to deploy Amazon Elastic Kubernetes Service (EKS) in the supported regions. The supported regions will be referred to in a later step.
+   - If you chose **Fixed price w/bring your own license (container offer - any supported Kubernetes platform)** in [Step 1. Select a billing plan for ScalarDB Analytics](#step-1-select-a-billing-plan-for-scalardb-analytics), you can use any of the supported Kubernetes platforms.
 
      :::note
 
@@ -109,7 +109,7 @@ Deploy a cluster on your preferred Kubernetes platform based on the following re
        <Tabs groupId="kubernetes" queryString>
          <TabItem value="eks" label="EKS" default>
            - If you chose **Fixed price w/ bring your own license (container offer - any supported Kubernetes platform)**, you can use Amazon Elastic Kubernetes Service (EKS).
-           - If you chose **Pay as you go (container offer - AWS Marketplace)** in [Step 1. Decide on the billing method for ScalarDB Analytics](#step-1-decide-on-the-billing-method-for-scalardb-analytics), you need to do the following:
+           - If you chose **Pay as you go (container offer - AWS Marketplace)** in [Step 1. Select a billing plan for ScalarDB Analytics](#step-1-select-a-billing-plan-for-scalardb-analytics), you need to do the following:
              1. Deploy EKS in supported regions that are described in the AWS documentation [MeterUsage Region support for Amazon ECS and Amazon EKS](https://docs.aws.amazon.com/marketplace/latest/APIReference/metering-regions.html#meterusage-region-support-ecs-eks).
              1. Run the following two commands after you deploy EKS:
                 - `eksctl utils associate-iam-oidc-provider`
@@ -226,9 +226,9 @@ Create your custom values file `scalardb-analytics-server.yaml` based on your en
 
 1. Set the container image and the license configurations
 
-   Based on the billing method you chose in [Step 1. Decide on the billing method for ScalarDB Analytics](#step-1-decide-on-the-billing-method-for-scalardb-analytics), set the container image configuration to `scalarDbAnalyticsServer.image.repository`. Select one of the following billing methods to see an example of this configuration.
+   Based on the billing plan you chose in [Step 1. Select a billing plan for ScalarDB Analytics](#step-1-select-a-billing-plan-for-scalardb-analytics), set the container image configuration to `scalarDbAnalyticsServer.image.repository`. Select one of the following billing plans to see an example of this configuration.
 
-   <Tabs groupId="billing-method" queryString>
+   <Tabs groupId="billing-plan" queryString>
      <TabItem value="payg-container-offer-aws-marketplace" label="Pay as you go (container offer - AWS Marketplace)" default>
      ```yaml
      scalarDbAnalyticsServer:
@@ -251,9 +251,9 @@ Create your custom values file `scalardb-analytics-server.yaml` based on your en
 
 1. Set the service account configurations
 
-   Based on the billing method you chose in [Step 1. Decide on the billing method for ScalarDB Analytics](#step-1-decide-on-the-billing-method-for-scalardb-analytics), set the service account configurations to `scalarDbAnalyticsServer.serviceAccount`. Select one of the following billing methods to see an example of this configuration.
+   Based on the billing plan you chose in [Step 1. Select a billing plan for ScalarDB Analytics](#step-1-select-a-billing-plan-for-scalardb-analytics), set the service account configurations to `scalarDbAnalyticsServer.serviceAccount`. Select one of the following billing plans to see an example of this configuration.
 
-   <Tabs groupId="billing-method" queryString>
+   <Tabs groupId="billing-plan" queryString>
      <TabItem value="payg-container-offer-aws-marketplace" label="Pay as you go (container offer - AWS Marketplace)" default>
      ```yaml
      scalarDbAnalyticsServer:

versioned_docs/version-3.16/scalardb-cluster/scalardb-cluster-configurations.mdx

@@ -1210,29 +1210,23 @@ For details about how to configure Spring Data JDBC for ScalarDB, see [Configura
 - **Description:** Maximum size of metadata allowed to be received.
 - **Default value:** The gRPC default value
 
-#### Authentication and authorization configurations
+### Authentication and authorization configurations
 
 The following shows the authentication and authorization configurations for the ScalarDB Cluster client.
 
-##### `auth.enabled`
+#### `auth.enabled`
 
 - **Field:** `scalar.db.cluster.auth.enabled`
 - **Description:** Whether authentication and authorization are enabled.
 - **Default value:** `false`
 
-:::warning
-
-If you enable authentication and authorization, you will also need to set [`scalar.db.cross_partition_scan.enabled`](#cross-partition-scan-configurations) to `true` for the system namespace (`scalardb` by default). This is because the ABAC feature performs cross-partition scans internally.
-
-:::
-
-##### `auth.username`
+#### `auth.username`
 
 - **Field:** `scalar.db.sql.cluster_mode.username`
 - **Description:** The username of the client.
 - **Default value:** empty
 
-##### `auth.password`
+#### `auth.password`
 
 - **Field:** `scalar.db.sql.cluster_mode.password`
 - **Description:** The password of the client.