AUTO: Docs repo sync - ScalarDB

versioned_docs/version-3.13/requirements.mdx

@@ -29,7 +29,7 @@ The following Java Development Kits (JDKs) are verified and supported.
 
 ### .NET
 
-ScalarDB is provided as a gRPC server called ScalarDB Cluster, which also has a [.NET client SDK](scalardb-cluster-dotnet-client-sdk/overview.mdx) that wraps the .NET client generated from the proto file.
+ScalarDB is provided as a gRPC server called ScalarDB Cluster, which also has a [.NET client SDK](scalardb-cluster-dotnet-client-sdk/index.mdx) that wraps the .NET client generated from the proto file.
 
 The following .NET versions are verified and supported:
 

versioned_docs/version-3.13/scalardb-cluster/run-non-transactional-storage-operations-through-scalardb-cluster.mdx

@@ -216,7 +216,7 @@ You can use the primary key or the secondary key in your Azure Cosmos DB account
   </TabItem>
 </Tabs>
 
-For a comprehensive list of configurations for ScalarDB, see [ScalarDB Configurations](configurations.mdx).
+For a comprehensive list of configurations for ScalarDB, see [ScalarDB Configurations](../configurations.mdx).
 
 ## Set up ScalarDB Cluster in standalone mode
 

versioned_docs/version-3.13/scalardb-cluster/run-non-transactional-storage-operations-through-sql-interface.mdx

@@ -215,7 +215,7 @@ You can use the primary key or the secondary key in your Azure Cosmos DB account
   </TabItem>
 </Tabs>
 
-For a comprehensive list of configurations for ScalarDB, see [ScalarDB Configurations](configurations.mdx).
+For a comprehensive list of configurations for ScalarDB, see [ScalarDB Configurations](../configurations.mdx).
 
 ## Set up ScalarDB Cluster in standalone mode
 

versioned_docs/version-3.13/scalardb-sql/grammar.mdx

@@ -546,7 +546,7 @@ The `SELECT` command retrieves records from the database. ScalarDB SQL creates a
 3. If you specify the indexed column value with the `equal to` (`=`) operator in the `WHERE` clause without the `ORDER BY` clause, the `SELECT` command will use an index `Scan` operation.
 4. For other cases, the `SELECT` command will be converted to a cross-partition `Scan` operation.
 
-You need to enable the cross-partition scan option and the cross-partition scan with filtering and ordering options if you want to flexibly retrieve records across partitions with arbitrary conditions and orderings. Currently, the ordering option is available only for JDBC databases. For details about configurations, see [Cross-partition scan configurations](../configurations.mdx#cross-partition-scan-configurations) and [ScalarDB SQL Configurations](./configurations.mdx).
+You need to enable the cross-partition scan option and the cross-partition scan with filtering and ordering options if you want to flexibly retrieve records across partitions with arbitrary conditions and orderings. Currently, the ordering option is available only for JDBC databases. For details about configurations, see [Cross-partition scan configurations](../configurations.mdx#cross-partition-scan-configurations) and [ScalarDB Cluster SQL configurations](../scalardb-cluster/developer-guide-for-scalardb-cluster-with-java-api.mdx#scalardb-cluster-sql-client-configurations).
 
 :::warning
 
@@ -1170,7 +1170,7 @@ UpsertStatement statement4 = StatementBuilder.upsertInto("ns", "tbl")
 
 The `UPDATE` command updates existing records in the database. You can specify any conditions in the `WHERE` clause to filter records. However, specifying a primary key uniquely as much as possible is recommended to avoid the cross-partition operation since it might cause performance and consistency issues, especially in non-JDBC databases. Because ScalarDB SQL creates an execution plan for an `UPDATE` command that uses a `Get` or `Scan` operation to identify the target records, the same rule is applied for the selection of records. To understand what kinds of `WHERE` clauses cause cross-partition operations and to avoid such operations, see [SELECT](#select).
 
-You need to enable the cross-partition scan option if you want to update all records across partitions without specifying the `WHERE` clause. You also need to enable the cross-partition scan with filtering option if you want to flexibly update records across partitions with arbitrary conditions in the `WHERE` clause. For details about configurations, see [Cross-partition scan configurations](../configurations.mdx#cross-partition-scan-configurations) and [ScalarDB SQL Configurations](./configurations.mdx).
+You need to enable the cross-partition scan option if you want to update all records across partitions without specifying the `WHERE` clause. You also need to enable the cross-partition scan with filtering option if you want to flexibly update records across partitions with arbitrary conditions in the `WHERE` clause. For details about configurations, see [Cross-partition scan configurations](../configurations.mdx#cross-partition-scan-configurations) and [ScalarDB Cluster SQL configurations](../scalardb-cluster/developer-guide-for-scalardb-cluster-with-java-api.mdx#scalardb-cluster-sql-client-configurations).
 
 :::warning
 
@@ -1397,7 +1397,7 @@ UpdateStatement statement9 =
 
 The `DELETE` command deletes records in the database. You can specify any conditions in the `WHERE` clause to filter records. However, specifying a primary key uniquely is recommended as much as possible to avoid the cross-partition operation since it might cause performance and consistency issues, especially in non-JDBC databases. Because ScalarDB SQL creates an execution plan for a `DELETE` command that uses a `Get` or `Scan` operation to identify the target records, the same rule is applied for the selection of records. To understand what kinds of `WHERE` clauses cause cross-partition operations and to avoid such operations, see [SELECT](#select).
 
-You need to enable the cross-partition scan option if you want to delete all records across partitions without specifying the `WHERE` clause. You also need to enable the cross-partition scan with filtering option if you want to flexibly delete records across partitions with arbitrary conditions in the `WHERE` clause. For details about configurations, see [Cross-partition scan configurations](../configurations.mdx#cross-partition-scan-configurations) and [ScalarDB SQL Configurations](./configurations.mdx).
+You need to enable the cross-partition scan option if you want to delete all records across partitions without specifying the `WHERE` clause. You also need to enable the cross-partition scan with filtering option if you want to flexibly delete records across partitions with arbitrary conditions in the `WHERE` clause. For details about configurations, see [Cross-partition scan configurations](../configurations.mdx#cross-partition-scan-configurations) and [ScalarDB Cluster SQL configurations](../scalardb-cluster/developer-guide-for-scalardb-cluster-with-java-api.mdx#scalardb-cluster-sql-client-configurations).
 
 :::warning
 

versioned_docs/version-3.13/schema-loader-import.mdx

@@ -78,7 +78,7 @@ The following is a sample schema for importing tables. For the sample schema fil
 }
 ```
 
-The import table schema consists of a namespace name, a table name, and a `transaction` field. The `transaction` field indicates whether the table will be imported for transactions or not. If you set the `transaction` field to `true` or don't specify the `transaction` field, this tool creates a table with transaction metadata if needed. If you set the `transaction` field to `false`, this tool imports a table without adding transaction metadata (that is, for a table using the [Storage API](storage-abstraction.mdx)).
+The import table schema consists of a namespace name, a table name, and a `transaction` field. The `transaction` field indicates whether the table will be imported for transactions or not. If you set the `transaction` field to `true` or don't specify the `transaction` field, this tool creates a table with transaction metadata if needed. If you set the `transaction` field to `false`, this tool imports a table without adding transaction metadata (that is, for a table using the [Storage API](run-non-transactional-storage-operations-through-primitive-crud-interface.mdx)).
 
 ## Data-type mapping from JDBC databases to ScalarDB
 

versioned_docs/version-3.13/schema-loader.mdx

@@ -463,7 +463,7 @@ The schema has table definitions that include `columns`, `partition-key`, `clust
 - The `secondary-index` field defines which columns are indexed.
 - The `transaction` field indicates whether the table is for transactions or not.
   - If you set the `transaction` field to `true` or don't specify the `transaction` field, this tool creates a table with transaction metadata if needed.
-  - If you set the `transaction` field to `false`, this tool creates a table without any transaction metadata (that is, for a table with [Storage API](storage-abstraction.mdx)).
+  - If you set the `transaction` field to `false`, this tool creates a table without any transaction metadata (that is, for a table with [Storage API](run-non-transactional-storage-operations-through-primitive-crud-interface.mdx)).
 
 You can also specify database or storage-specific options in the table definition as follows: