Apply suggestions from code review

Co-authored-by: William Richter <88400283+WRRicht3r@users.noreply.github.com>
Signed-off-by: Ekaterina Mekhnetsova <mekkatya@gmail.com>

Author: 2 people

src/guide/bash.md

@@ -116,7 +116,7 @@ Make sure you bring up the test network as well.
 Now let's look at how to properly configure Iroha 2, and especially its
 **C**ommand-**L**ine **I**nterface client.
 
-Make sure that you have another terminal tab or window with a running
+Make sure that you have another terminal tab or window open with a running
 version, using the instructions above. You can use this screen to monitor
 the pipeline events as they are output.
 
@@ -281,7 +281,7 @@ Another way to create a user (and the user's keys) is as follows:
    ./target/debug/iroha_crypto_cli
    ```
 
-2. Copy the public key and repeat the instructions for registering a new
+2. Copy the public key and repeat the instructions to register a new
    account. Every time you run this command, you will generate a new
    key-pair.
 

src/guide/javascript.md

@@ -20,8 +20,8 @@ The Iroha 2 JavaScript library consists of multiple packages:
 | <code class="whitespace-pre">crypto-target-bundler</code> | Provides compiled crypto WASM to use with bundlers such as Webpack                                                                                 |
 
 All of these are published under the `@iroha2` scope into Iroha Nexus
-Registry. In future, they will be published in the main NPM Registry. To
-install these packages, firstly you need to setup a registry:
+Registry. In the future, they will be published in the main NPM Registry. To
+install these packages, you first need to set up a registry:
 
 ```ini
 # FILE: .npmrc
@@ -39,8 +39,8 @@ pnpm add @iroha2/crypto-target-web
 The set of packages that you need to install depends on your intention.
 Maybe you only need to play with the Data Model to perform
 (de-)serialisation, in which case the `data-model` package is enough. If
-you only need to check on a peer in terms of its status or health, you need
-only the client library, because this API doesn't require any interactions
+you only need to check on a peer in terms of its status or health, you  just need
+the client library, because this API doesn't require any interactions
 with crypto or Data Model.
 
 For the purposes of this tutorial, it's better to install everything.
@@ -77,7 +77,7 @@ any convenience features like a `TransactionBuilder` or a `ConfigBuilder`.
 ::: info
 
 The work on implementing those is underway, and these features will very
-likely be available with the second round of this tutorial's release.
+likely be available in the second round of this tutorial's release.
 
 :::
 
@@ -782,7 +782,7 @@ onBeforeUnmount(stopListening)
 </template>
 ```
 
-That's it! Finally, we should only wrap it up with the `App.vue` component
+That's it! Finally, we just need to wrap it up with the `App.vue` component
 and the `app` entrypoint:
 
 ```vue

src/guide/kotlin-java.md

@@ -14,7 +14,7 @@ that you know how to build and deploy your program on the target platforms.
 The Iroha 2 JVM-compatible SDKs are as much a work-in-progress as the rest
 of this guide, and significantly more so than the Rust library.
 
-Without further ado, here's an example `build.gradle` file:
+Without further ado, here's the example `build.gradle` file:
 
 ```kotlin
 allprojects {

src/guide/rust.md

@@ -428,6 +428,6 @@ for event in iroha_client.listen_for_events(filter)? {
 };
 ```
 
-Needless to say that a synchronous infinite blocking loop is bad UX for
+Needless to say, an synchronous infinite blocking loop is bad UX for
 anything but a command-line program, but for illustration purposes, this
 would create a nice printout, just like in `iroha_client_cli`.