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

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

Author: github-actions[bot]

docs/scalardb-cluster/getting-started-with-vector-search.mdx

@@ -61,11 +61,7 @@ This tutorial has been tested with OpenJDK from Eclipse Temurin. ScalarDB itself
 Create the following configuration file as `scalardb-cluster-node.properties`, replacing `<YOUR_LICENSE_KEY>` and `<LICENSE_CHECK_CERT_PEM>` with your ScalarDB license key and license check certificate values. For more information about the license key and certificate, see [How to Configure a Product License Key](../scalar-licensing/README.mdx).
 
 ```yaml
-# Storage configurations
-scalar.db.storage=jdbc
-scalar.db.contact_points=jdbc:postgresql://postgresql:5432/postgres
-scalar.db.username=postgres
-scalar.db.password=postgres
+scalar.db.transaction.enabled=false
 
 # Enable the standalone mode
 scalar.db.cluster.node.standalone_mode.enabled=true
@@ -333,20 +329,6 @@ Create the following configuration file as `docker-compose.yaml`.
 
 ```yaml
 services:
-  postgresql:
-    container_name: "postgresql"
-    image: "postgres:15"
-    ports:
-      - 5432:5432
-    environment:
-      - POSTGRES_PASSWORD=postgres
-    healthcheck:
-      test: ["CMD-SHELL", "pg_isready || exit 1"]
-      interval: 1s
-      timeout: 10s
-      retries: 60
-      start_period: 30s
-
   scalardb-cluster-standalone:
     container_name: "scalardb-cluster-node"
     image: "ghcr.io/scalar-labs/scalardb-cluster-node-byol-premium:3.15.2"
@@ -355,14 +337,11 @@ services:
       - 9080:9080
     volumes:
       - ./scalardb-cluster-node.properties:/scalardb-cluster/node/scalardb-cluster-node.properties
-    depends_on:
-      postgresql:
-        condition: service_healthy
 ```
 
-### 3. Start PostgreSQL and ScalarDB Cluster
+### 3. Start ScalarDB Cluster
 
-Run the following command to start PostgreSQL and ScalarDB Cluster in standalone mode.
+Run the following command to start ScalarDB Cluster in standalone mode.
 
 ```console
 docker compose up -d

docs/scalardb-cluster/scalardb-cluster-configurations.mdx

@@ -32,6 +32,7 @@ The basic configurations for a cluster node are as follows:
 | `scalar.db.metadata.cache_expiration_time_secs`                   | ScalarDB has a metadata cache to reduce the number of requests to the database. This setting specifies the expiration time of the cache in seconds. If you specify `-1`, the cache will never expire.          | `60`                   |
 | `scalar.db.active_transaction_management.expiration_time_millis`  | ScalarDB Cluster nodes maintain ongoing transactions, which can be resumed by using a transaction ID. This configuration specifies the expiration time of this transaction management feature in milliseconds. | `60000` (60 seconds)   |
 | `scalar.db.system_namespace_name`                                 | The given namespace name will be used by ScalarDB internally.                                                                                                                                                  | `scalardb`             |
+| `scalar.db.transaction.enabled`                                   | Whether the transaction feature is enabled. For example, if you use only the embedding feature, you can set this property to `false`.                                                                          | `true`                 |
 
 ## Transaction manager configurations