Update commands name

Author: dongwon8247

README.md

@@ -41,8 +41,8 @@ You can read the docs in [Gitbook](https://onbloc.gitbook.io/gnoland-developer-p
       * [Common Parameters](docs/cli/common-parameters.md)
       * [gnokey](docs/cli/gnokey.md)
       * [gnoland](docs/cli/gnoland.md)
-      * [gnotxport](docs/cli/gnotxport.md)
-      * [gnodev](docs/cli/gnodev.md)
+      * [tm2txsync](docs/cli/tm2txsync.md)
+      * [gno](docs/cli/gno.md)
       * [gnofaucet](docs/cli/gnofaucet.md)
     * [Gnoland RPC Endpoints](docs/gnoland-rpc-endpoints.md)
 * Tutorials

SUMMARY.md

@@ -35,8 +35,8 @@
   * [Common Parameters](docs/cli/common-parameters.md)
   * [gnokey](docs/cli/gnokey.md)
   * [gnoland](docs/cli/gnoland.md)
-  * [gnotxport](docs/cli/gnotxport.md)
-  * [gnodev](docs/cli/gnodev.md)
+  * [tm2txsync](docs/cli/tm2txsync.md)
+  * [gno](docs/cli/gno.md)
   * [gnofaucet](docs/cli/gnofaucet.md)
 * [Gnoland RPC Endpoints](docs/gnoland-rpc-endpoints.md)
 

docs/building-a-realm/deploy-and-call-realms.md

@@ -3,13 +3,13 @@
 There are two methods of deploying and calling realms. 
 
 1. With the blockchain: You can use the subcommands of [`gnokey`](../cli/gnokey.md) such as [`addpkg`](../cli/gnokey.md#subcommands), to deploy a realm to the Gnoland blockchain, and [`maketx call`](../cli/gnokey.md#call), to call available realms in the Gnoland blockchain.
-2. Without a blockchain: You can use [`gnodev`](../cli/gnodev.md), which allows you to use the GnoVM without a blockchain in a local environment. This method is fast and allows you to use development patterns such as TDD. However, it does not facilitate the capability for external parties to participate in testing since it's done locally.
+2. Without a blockchain: You can use [`gno`](../cli/gno.md), which allows you to use the GnoVM without a blockchain in a local environment. This method is fast and allows you to use development patterns such as TDD. However, it does not facilitate the capability for external parties to participate in testing since it's done locally.
 
 This section covers how to deploy and call realms with the first method - With the blockchain.
 
 ## Deploy
 
-Use the `addpkg`, a subcommand of [`gnokey`](../cli/gnodev.md), to publicly deploy realms.
+Use the `addpkg`, a subcommand of [`gnokey`](../cli/gno.md), to publicly deploy realms.
 
 <figure><img src="../../.gitbook/assets/img05.png" alt=""><figcaption></figcaption></figure>
 

docs/building-a-realm/realm-examples/hello.gno.md

@@ -62,7 +62,7 @@ func Test(t *testing.T) {
 }
 ```
 
-Let's test the code using `gnodev test`.
+Let's test the code using `gno test`.
 
 <figure><img src="../../../.gitbook/assets/gor_01_01_test.png" alt=""><figcaption></figcaption></figure>
 

docs/building-a-realm/realm-examples/realm.gno.md

@@ -1,6 +1,6 @@
 # realm.gno
 
-The `realm` realm provides a guide on how to import packages in a test environment (`gnodev`) and the production environment (`gnokey addpkg`) along with precautions to note.
+The `realm` realm provides a guide on how to import packages in a test environment (`gno`) and the production environment (`gnokey addpkg`) along with precautions to note.
 
 
 
@@ -32,7 +32,7 @@ Next, we'll import the package above in both the test environment and the produc
 
 ### **Importing in the test environment**
 
-In the test environment, we will copy the file, as `gnodev` imports the package with the physical file path.
+In the test environment, we will copy the file, as `gno` imports the package with the physical file path.
 
 <figure><img src="../../../.gitbook/assets/gor_04_01_pkg_01.png" alt=""><figcaption></figcaption></figure>
 
@@ -119,7 +119,7 @@ func TestGetPrivateVar(t *testing.T) {
 
 <figure><img src="../../../.gitbook/assets/gor_04_02_gnodev.png" alt=""><figcaption></figcaption></figure>
 
-We can confirm that the test has been successfully passed in the test environment using `gnodev`.&#x20;
+We can confirm that the test has been successfully passed in the test environment using `gno`.&#x20;
 
 
 
@@ -137,7 +137,7 @@ Calling `Render()` and `GetPublicVar()` using the `gnokey maketx call` also work
 
 <figure><img src="../../../.gitbook/assets/gor_04_06_call_get_private.png" alt=""><figcaption></figcaption></figure>
 
-However, unlike the results in `gnodev`, we run into an issue when calling the `getPrivateVar()` function using the `gnokey maketx call` command in the production environment.
+However, unlike the results in `gno`, we run into an issue when calling the `getPrivateVar()` function using the `gnokey maketx call` command in the production environment.
 
 
 
@@ -147,4 +147,4 @@ On the other hand, calling the `getPrivateVar()` function using the `gnokey quer
 
 
 
-> **Note:** As of testnet3, we have run into unexpected results when using access modifiers with `gnodev`, `maketx`, and `query`. We suspect the cause to be one of the following: GnoVM, Gnokey Query, or Gnodev. For now, we can get around this error by changing the lowercase to the uppercase to publicly access the functions. We will update this section once we determine the cause of this phenomenon.
+> **Note:** As of testnet3, we have run into unexpected results when using access modifiers with `gno`, `maketx`, and `query`. We suspect the cause to be one of the following: GnoVM, Gnokey Query, or gno. For now, we can get around this error by changing the lowercase to the uppercase to publicly access the functions. We will update this section once we determine the cause of this phenomenon.

docs/building-a-realm/testing-realms.md

@@ -3,7 +3,7 @@
 There are two methods for testing a realm or package during the development phase.
 
 1. Calling the realm/packages after deploying it on a local network (or testnet3).
-2. Using the `test` option of [`gnodev`](../cli/gnodev.md).
+2. Using the `test` option of [`gno`](../cli/gno.md).
 
 While the first method is recommended for its accuracy and similarity to the actual deployment environment, it is more efficient to initially utilize the second method for composing test cases and then proceed to the first method if no errors are detected.
 
@@ -15,7 +15,7 @@ Writing test cases in Gnolang is similar to that of Golang, with general rules a
 * The function name of test cases must start with `Test`.
 * The `t *testing.T` argument must be included.
   * The `testing` package must be imported.
-* Tests must be run with the `gnodev test` command.
+* Tests must be run with the `gno test` command.
 
 
 
@@ -65,7 +65,7 @@ Two conditions exist in the test case above.
 1. "Hello People!" should be returned when calling `Hello("People")`.
 2. "Hello People!" should be returned when calling `Hello("")`.
 
-<figure><img src="../../.gitbook/assets/img04.png" alt=""><figcaption><p>Testing with <code>gnodev</code></p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/img04.png" alt=""><figcaption><p>Testing with <code>gno</code></p></figcaption></figure>
 
 Upon examination of our realm code and the associated test results, the initial condition exhibited the desired behavior. However, an error was identified in the second condition. Despite the expected outcome of "Hello" being returned, the test case incorrectly specified that the expected output should be "Hello People!" instead.
 

docs/cli/README.md

@@ -5,7 +5,7 @@ This section lists available Gno commands.
 * [Common Parameters](common-parameters.md)
 * [gnokey](gnokey.md) - used primarily for key management, but also for general interactions with gnoland
 * [gnoland](gnoland.md) - used for running a blockchain node
-* [gnotxport](gnotxport.md) - used for importing and exporting transactions from the local blockchain node storage
-* [gnodev](gnodev.md) - a handy tool for developing and prototyping gno packages / realms
+* [tm2txsync](tm2txsync.md) - used for importing and exporting transactions from the local blockchain node storage
+* [gno](gno.md) - a handy tool for developing and prototyping gno packages / realms
 * [gnofaucet](gnofaucet.md) - serves as a faucet for GNOT, the native network currency
 

docs/cli/gnodev.md renamed to docs/cli/gno.md

@@ -1,13 +1,13 @@
-# gnodev
+# gno (ex gnodev)
 
-`gnodev` is a handy tool for developing and prototyping Gno packages and realms. You may use `gnodev` to use the GnoVM without an actual blockchain to build or test realms in a local environment.
+`gno` is a handy tool for developing and prototyping Gno packages and realms. You may use `gno` to use the GnoVM without an actual blockchain to build or test realms in a local environment.
 
-## Run `gnodev` Commands
+## Run `gno` Commands
 
-The following command will run `gnodev`.
+The following command will run `gno`.
 
 ```bash
-$ gnodev {SUB_COMMAND}
+$ gno {SUB_COMMAND}
 ```
 
 **Subcommands**
@@ -35,7 +35,7 @@ $ gnodev {SUB_COMMAND}
 | Name         | Type          | Description                                                           |
 | ------------ | ------------- | --------------------------------------------------------------------- |
 | `verbose`    | Boolean       | Displays extended information.                                        |
-| `root-dir`   | String        | Clones location of github.com/gnolang/gno (gnodev tries to guess it). |
+| `root-dir`   | String        | Clones location of github.com/gnolang/gno (gno tries to guess it). |
 | `run`        | String        | Test name filtering pattern.                                          |
 | `timeout`    | time.Duration | The maximum execution time in ns.                                     |
 | `precompile` | Boolean       | Precompiles a `.gno` file to a `.go` file before testing.             |
@@ -59,4 +59,4 @@ $ gnodev {SUB_COMMAND}
 | Name       | Type    | Description                                                           |
 | ---------- | ------- | --------------------------------------------------------------------- |
 | `verbose`  | Boolean | Displays extended information.                                        |
-| `root-dir` | String  | Clones location of github.com/gnolang/gno (gnodev tries to guess it). |
+| `root-dir` | String  | Clones location of github.com/gnolang/gno (gno tries to guess it). |

docs/cli/gnotxport.md renamed to docs/cli/tm2txsync.md

@@ -1,13 +1,13 @@
-# gnotxport
+# tm2txsync
 
-`gnotxport` is used for backing up a local node's transactions.
+`tm2txsync` is used for backing up a local node's transactions.
 
 ## Import Transaction Data To (or Export It From) a Node
 
 You may import or export transaction data with the following command.
 
 ```bash
-$ gnotxport {SUB_COMMAND}
+$ tm2txsync {SUB_COMMAND}
 ```
 
 #### **Subcommands**

docs/standard-libraries.md

@@ -48,7 +48,7 @@ type Coin struct {
 
 ### `testing`
 
-A library that declares `*testing`, which is a tool used for the creation and execution of test cases during the development and testing phase of realms utilizing the `gnodev` CLI tool with the `test` option.
+A library that declares `*testing`, which is a tool used for the creation and execution of test cases during the development and testing phase of realms utilizing the `gno` CLI tool with the `test` option.
 
 There are 3 types of testing in `gno`.