AUTO: Sync ScalarDL docs in English to docs site repo

Author: josh-wong

docs/getting-started-hashstore.mdx

@@ -37,7 +37,7 @@ Then, download the tools by running the following command:
 ```console
 curl -OL https://github.com/scalar-labs/scalardl/releases/download/v$VERSION/scalardl-hashstore-java-client-sdk-$VERSION.zip
 unzip scalardl-hashstore-java-client-sdk-$VERSION.zip
-mv scalardl-hashstore-java-client-sdk-$VERSION client
+mv scalardl-hashstore-java-client-sdk-$VERSION hashstore
 ```
 
 ## Configure the client properties
@@ -73,7 +73,7 @@ Do not use the sample private key and certificate in production environments. Fo
 Next, you can bootstrap HashStore by running the following command:
 
 ```console
-client/bin/scalardl-hashstore bootstrap --properties client.properties
+hashstore/bin/scalardl-hashstore bootstrap --properties client.properties
 ```
 
 The bootstrap command internally registers identity information (a certificate or secret) and predefined contracts necessary to use HashStore.
@@ -104,7 +104,7 @@ You should get the following hash value:
 You can put the hash value by running the following command:
 
 ```console
-client/bin/scalardl-hashstore put-object --properties client.properties \
+hashstore/bin/scalardl-hashstore put-object --properties client.properties \
 --object-id a.txt \
 --hash 5c7440fb2273a247f78aadefbc511c680a84e7d44004abfaedef2b145151dab0 \
 --metadata '{"note": "created"}'
@@ -126,7 +126,7 @@ b97a42c87a46ffebe1439f8c1cd2f86e2f9b84dad89c8e9ebb257a19b6fdfe1c  a.txt
 You can then update the hash value as follows:
 
 ```console
-client/bin/scalardl-hashstore put-object --properties client.properties \
+hashstore/bin/scalardl-hashstore put-object --properties client.properties \
 --object-id a.txt \
 --hash b97a42c87a46ffebe1439f8c1cd2f86e2f9b84dad89c8e9ebb257a19b6fdfe1c \
 --metadata '{"note": "updated"}'
@@ -135,7 +135,7 @@ client/bin/scalardl-hashstore put-object --properties client.properties \
 You can also get the latest status of the object by running the following command:
 
 ```console
-client/bin/scalardl-hashstore get-object --properties client.properties \
+hashstore/bin/scalardl-hashstore get-object --properties client.properties \
 --object-id a.txt
 ```
 
@@ -163,7 +163,7 @@ If you cannot get the hash value of the older version of the `a.txt` file in you
 :::
 
 ```console
-client/bin/scalardl-hashstore compare-object-versions --properties client.properties \
+hashstore/bin/scalardl-hashstore compare-object-versions --properties client.properties \
 --object-id a.txt \
 --versions '[{"version_id": "v2", "hash_value": "b97a42c87a46ffebe1439f8c1cd2f86e2f9b84dad89c8e9ebb257a19b6fdfe1c"}, {"version_id": "v1", "hash_value": "5c7440fb2273a247f78aadefbc511c680a84e7d44004abfaedef2b145151dab0"}]}'
 ```
@@ -189,7 +189,7 @@ Alice updated this file
 Now the hash value of the latest version is `1f75d715648a3b4b3a33ecd7428a3e7139d9357da7d38735c23bf38618ecf9c7`. You can execute validation by running the following command:
 
 ```console
-client/bin/scalardl-hashstore compare-object-versions --properties client.properties \
+hashstore/bin/scalardl-hashstore compare-object-versions --properties client.properties \
 --object-id a.txt \
 --versions '[{"version_id": "v2", "hash_value": "1f75d715648a3b4b3a33ecd7428a3e7139d9357da7d38735c23bf38618ecf9c7"}, {"version_id": "v1", "hash_value": "5c7440fb2273a247f78aadefbc511c680a84e7d44004abfaedef2b145151dab0"}]}'
 ```
@@ -220,7 +220,7 @@ For example, in object authenticity management, the `put-object` command (and th
 The third step above must be done in an ACID manner by executing the following command with the `--put-to-mutable` option:
 
 ```console
-client/bin/scalardl-hashstore put-object --properties client.properties \
+hashstore/bin/scalardl-hashstore put-object --properties client.properties \
 --object-id a.txt \
 --hash 5c7440fb2273a247f78aadefbc511c680a84e7d44004abfaedef2b145151dab0 \
 --put-to-mutable '{...}'
@@ -256,7 +256,7 @@ If a system cannot guarantee that an audit set has not been changed unexpectedly
 You can create a collection for an audit set by running the following command:
 
 ```console
-client/bin/scalardl-hashstore create-collection --properties client.properties \
+hashstore/bin/scalardl-hashstore create-collection --properties client.properties \
 --collection-id audit_set --object-ids a.txt --object-ids b.txt
 ```
 
@@ -265,21 +265,21 @@ The collection ID must be a unique ID that identifies the collection. You can sp
 You can also add objects to the collection by running the following command:
 
 ```console
-client/bin/scalardl-hashstore add-to-collection --properties client.properties \
+hashstore/bin/scalardl-hashstore add-to-collection --properties client.properties \
 --collection-id audit_set --object-ids c.txt --object-ids d.txt
 ```
 
 And you can remove objects from the collection by running the following command:
 
 ```console
-client/bin/scalardl-hashstore remove-from-collection --properties client.properties \
+hashstore/bin/scalardl-hashstore remove-from-collection --properties client.properties \
 --collection-id audit_set --object-ids a.txt
 ```
 
 You can get the latest status of the collection by running the following command:
 
 ```console
-client/bin/scalardl-hashstore get-collection --properties client.properties \
+hashstore/bin/scalardl-hashstore get-collection --properties client.properties \
 --collection-id audit_set
 ```
 
@@ -293,7 +293,7 @@ Result:
 To confirm that the audit set has not been changed unexpectedly, you can check the update history of the audit set by running the following command:
 
 ```console
-client/bin/scalardl-hashstore get-collection-history --properties client.properties \
+hashstore/bin/scalardl-hashstore get-collection-history --properties client.properties \
 --collection-id audit_set
 ```
 
@@ -326,7 +326,7 @@ In ScalarDL, you occasionally need to validate your data to make sure all the da
 You can validate an object by running the following command:
 
 ```console
-client/bin/scalardl-hashstore validate-ledger --properties client.properties \
+hashstore/bin/scalardl-hashstore validate-ledger --properties client.properties \
 --object-id a.txt
 ```
 
@@ -349,7 +349,7 @@ You should get a result like the following:
 You can validate a collection by running the following command:
 
 ```console
-client/bin/scalardl-hashstore validate-ledger --properties client.properties \
+hashstore/bin/scalardl-hashstore validate-ledger --properties client.properties \
 --collection-id audit_set
 ```
 

docs/getting-started-tablestore.mdx

@@ -35,7 +35,7 @@ Then, download the tools by running the following command:
 ```console
 curl -OL https://github.com/scalar-labs/scalardl/releases/download/v$VERSION/scalardl-tablestore-java-client-sdk-$VERSION.zip
 unzip scalardl-tablestore-java-client-sdk-$VERSION.zip
-mv scalardl-tablestore-java-client-sdk-$VERSION client
+mv scalardl-tablestore-java-client-sdk-$VERSION tablestore
 ```
 
 ## Configure the client properties
@@ -71,7 +71,7 @@ Do not use the sample private key and certificate in production environments. Fo
 Next, you can bootstrap TableStore by running the following command:
 
 ```console
-client/bin/scalardl-tablestore bootstrap --properties client.properties
+tablestore/bin/scalardl-tablestore bootstrap --properties client.properties
 ```
 
 The bootstrap command internally registers identity information (a certificate or secret) and predefined contracts necessary to use TableStore.
@@ -91,11 +91,11 @@ Now you can execute SQL statements with TableStore. In this section, you'll try
 You can create the sample table by running the following commands:
 
 ```console
-client/bin/scalardl-tablestore execute-statement --properties client.properties \
+tablestore/bin/scalardl-tablestore execute-statement --properties client.properties \
 --statement "CREATE TABLE employee (id STRING PRIMARY KEY, department STRING)"
 ```
 ```console
-client/bin/scalardl-tablestore execute-statement --properties client.properties \
+tablestore/bin/scalardl-tablestore execute-statement --properties client.properties \
 --statement "CREATE TABLE department (id STRING PRIMARY KEY)"
 ```
 
@@ -104,7 +104,7 @@ When creating a table, you need to specify the name and the primary key. You can
 You can show the created tables by running the following command:
 
 ```console
-client/bin/scalardl-tablestore execute-statement --properties client.properties \
+tablestore/bin/scalardl-tablestore execute-statement --properties client.properties \
 --statement "SELECT * FROM information_schema.tables"
 ```
 
@@ -133,26 +133,26 @@ Result:
 Next, insert several `employee` records by running the following commands:
 
 ```console
-client/bin/scalardl-tablestore execute-statement --properties client.properties \
+tablestore/bin/scalardl-tablestore execute-statement --properties client.properties \
 --statement "INSERT INTO employee VALUES {'id': '1001', 'name': 'Alice', 'department': 'sales', 'salary': 654.3}"
 ```
 ```console
-client/bin/scalardl-tablestore execute-statement --properties client.properties \
+tablestore/bin/scalardl-tablestore execute-statement --properties client.properties \
 --statement "INSERT INTO employee VALUES {'id': '1002', 'name': 'Bob', 'department': 'sales', 'salary': 543.2}"
 ```
 ```console
-client/bin/scalardl-tablestore execute-statement --properties client.properties \
+tablestore/bin/scalardl-tablestore execute-statement --properties client.properties \
 --statement "INSERT INTO employee VALUES {'id': '1003', 'name': 'Carol', 'department': 'engineering', 'salary': 654.3}"
 ```
 
 Insert the corresponding `department` records as well by running the following commands:
 
 ```console
-client/bin/scalardl-tablestore execute-statement --properties client.properties \
+tablestore/bin/scalardl-tablestore execute-statement --properties client.properties \
 --statement "INSERT INTO department VALUES {'id': 'sales', 'location': 'Shinjuku', 'phone': '000-1234'}"
 ```
 ```console
-client/bin/scalardl-tablestore execute-statement --properties client.properties \
+tablestore/bin/scalardl-tablestore execute-statement --properties client.properties \
 --statement "INSERT INTO department VALUES {'id': 'engineering', 'location': 'Shibuya', 'phone': '000-4321'}"
 ```
 
@@ -161,7 +161,7 @@ client/bin/scalardl-tablestore execute-statement --properties client.properties
 Then, check the inserted records. You need to specify at least a primary key or index key to select records. For example, you can get an `employee` record by specifying the primary key by running the following command:
 
 ```console
-client/bin/scalardl-tablestore execute-statement --properties client.properties \
+tablestore/bin/scalardl-tablestore execute-statement --properties client.properties \
 --statement "SELECT id, name, department FROM employee WHERE id = '1001'"
 ```
 
@@ -179,7 +179,7 @@ Result:
 You can also specify an index key to select records by running the following command:
 
 ```console
-client/bin/scalardl-tablestore execute-statement --properties client.properties \
+tablestore/bin/scalardl-tablestore execute-statement --properties client.properties \
 --statement "SELECT id, name, department FROM employee WHERE department = 'sales'"
 ```
 
@@ -201,7 +201,7 @@ Result:
 If you want to filter records, specify additional conditions by running the following command:
 
 ```console
-client/bin/scalardl-tablestore execute-statement --properties client.properties \
+tablestore/bin/scalardl-tablestore execute-statement --properties client.properties \
 --statement "SELECT id, name, department FROM employee WHERE department = 'sales' AND salary < 600"
 ```
 
@@ -220,7 +220,7 @@ Result:
 You can also join the two tables by running the following command:
 
 ```console
-client/bin/scalardl-tablestore execute-statement --properties client.properties \
+tablestore/bin/scalardl-tablestore execute-statement --properties client.properties \
 --statement "SELECT * FROM employee JOIN department ON employee.department = department.id WHERE employee.department = 'engineering'"
 ```
 
@@ -244,7 +244,7 @@ Result:
 You can update the `employee` records by running the following command:
 
 ```console
-client/bin/scalardl-tablestore execute-statement --properties client.properties \
+tablestore/bin/scalardl-tablestore execute-statement --properties client.properties \
 --statement "UPDATE employee SET salary = 754.3 WHERE department = 'engineering'"
 ```
 
@@ -255,7 +255,7 @@ Make sure to specify at least a primary key or an index key to update the record
 You can get the update history of a record by running the following command:
 
 ```console
-client/bin/scalardl-tablestore execute-statement --properties client.properties \
+tablestore/bin/scalardl-tablestore execute-statement --properties client.properties \
 --statement "SELECT history() FROM employee WHERE id = '1003'"
 ```
 
@@ -285,7 +285,7 @@ Result:
 If you want to limit the number of versions (ages), specify the `LIMIT` clause by running the following command:
 
 ```console
-client/bin/scalardl-tablestore execute-statement --properties client.properties \
+tablestore/bin/scalardl-tablestore execute-statement --properties client.properties \
 --statement "SELECT history() FROM employee WHERE id = '1003' LIMIT 1"
 ```
 
@@ -311,7 +311,7 @@ In ScalarDL, you occasionally need to validate your data to make sure all the da
 You can validate the table schema by running the following command:
 
 ```console
-client/bin/scalardl-tablestore validate-ledger --properties client.properties \
+tablestore/bin/scalardl-tablestore validate-ledger --properties client.properties \
 --table-name employee
 ```
 
@@ -334,7 +334,7 @@ You should get a result like the following:
 You can validate the record by running the following command:
 
 ```console
-client/bin/scalardl-tablestore validate-ledger --properties client.properties \
+tablestore/bin/scalardl-tablestore validate-ledger --properties client.properties \
 --table-name employee --primary-key-column-name id --column-value '"1001"'
 ```
 
@@ -363,7 +363,7 @@ You should get a result like the following:
 You can validate the index record by running the following command:
 
 ```console
-client/bin/scalardl-tablestore validate-ledger --properties client.properties \
+tablestore/bin/scalardl-tablestore validate-ledger --properties client.properties \
 --table-name employee --index-key-column-name department --column-value '"sales"'
 ```