Correction after review

README.md

@@ -178,7 +178,7 @@ Then you can spawn the network by running the following command:
 ❯ ./zombienet-macos spawn --provider native examples/0001-small-network.toml
 ```
 
-**Note:** before spawning network one needs to varify that `kubectl`'s namespace is set to `default`
+**Note:** before spawning network one needs to verify that `kubectl`'s namespace is set to `default`
 ```bash
 ❯ kubectl config get-contexts
 

docs/book/cli/spawn.html

@@ -168,18 +168,6 @@ <h1 id="spawning"><a class="header" href="#spawning">Spawning</a></h1>
 </code></pre>
 <p>Then you can spawn the network by running the following command:</p>
 <pre><code class="language-bash">./zombienet-macos spawn examples/0001-small-network.toml
-</code>
-</pre>
-<blockquote><p>Note: before spawning network one needs to varify that <code>kubectl</code>'s namespace is set to <code>default</code></p></blockquote>
-<pre><code class="language-bash">
-❯ kubectl config get-contexts
-
-CURRENT   NAME                                      CLUSTER          AUTHINFO         NAMESPACE
-*         docker-desktop                            docker-desktop   docker-desktop   default
-
-# if not then set it to default value
-
-❯ kubectl config set-context --current --namespace='default'
 </code></pre>
 <p>You can follow the output of the <code>steps</code> to spawn the network and once the network is launched a message with the <code>node</code>s information like this one is show</p>
 <pre><code class="language-bash">┌───────────────────────────────────────────────────────────────────────────────────────────────────────────────┐

docs/book/guide.html

@@ -350,17 +350,6 @@ <h2 id="intro"><a class="header" href="#intro">Intro</a></h2>
               <em>current</em> constraints for both network configurations and
               test specifications.
             </p>
-            <blockquote><p>Note: before spawning network one needs to varify that <code>kubectl</code>'s namespace is set to <code>default</code></p></blockquote>
-<pre><code class="language-bash">
-❯ kubectl config get-contexts
-
-CURRENT   NAME                                      CLUSTER          AUTHINFO         NAMESPACE
-*         docker-desktop                            docker-desktop   docker-desktop   default
-
-# if not then set it to default value
-
-❯ kubectl config set-context --current --namespace='default'
-</code></pre>
             <h3 id="example-1---small-network-2-validators-1-parachain">
               <a
                 class="header"

docs/book/print.html

@@ -615,17 +615,6 @@ <h1 id="spawning">
               Then you can spawn the network by running the following command:
             </p>
             <pre><code class="language-bash">./zombienet-macos spawn examples/0001-small-network.toml
-</code></pre>
-<blockquote><p>NOTE: before spawning network one needs to varify that <code>kubectl</code>'s namespace is set to <code>default</code></p></blockquote>
-<pre><code class="language-bash">
-❯ kubectl config get-contexts
-
-CURRENT   NAME                                      CLUSTER          AUTHINFO         NAMESPACE
-*         docker-desktop                            docker-desktop   docker-desktop   default
-
-# if not then set it to default value
-
-❯ kubectl config set-context --current --namespace='default'
 </code></pre>
             <p>
               You can follow the output of the <code>steps</code> to spawn the

docs/src/cli/spawn.md

@@ -33,7 +33,7 @@ Then you can spawn the network by running the following command:
 ./zombienet-macos spawn examples/0001-small-network.toml
 ```
 
-**Note:** before spawning network one needs to varify that `kubectl`'s namespace is set to `default`
+**Note:** before spawning network one needs to verify that `kubectl`'s namespace is set to `default`
 ```bash
 ❯ kubectl config get-contexts
 

docs/src/cli/testing.md

@@ -5,7 +5,7 @@ Those assertions should be defined in a _feature test_, and the `dsl` and format
 
 The following is a small example to spawn a network (using the previous `simple network definition`) and assert that:
 
-**Note:** before spawning network one needs to varify that `kubectl`'s namespace is set to `default`
+**Note:** before spawning network one needs to verify that `kubectl`'s namespace is set to `default`
 ```bash
 ❯ kubectl config get-contexts
 

docs/src/guide.md

@@ -6,7 +6,7 @@ Zombienet was designed to be a flexible and easy to use tool, allowing users to
 
 In this guide we will go through simple use cases as well as more complex ones, describing the trade-offs made and the _current_ constraints for both network configurations and test specifications.
 
-**Note:** before spawning network one needs to varify that `kubectl`'s namespace is set to `default`
+**Note:** before spawning network one needs to verify that `kubectl`'s namespace is set to `default`
 ```bash
 ❯ kubectl config get-contexts
 

javascript/README.md

@@ -177,7 +177,7 @@ Then you can spawn the network by running the following command:
 ❯ ./zombienet-macos spawn --provider native examples/0001-small-network.toml
 ```
 
-**Note:** before spawning network one needs to varify that `kubectl`'s namespace is set to `default`
+**Note:** before spawning network one needs to verify that `kubectl`'s namespace is set to `default`
 ```bash
 ❯ kubectl config get-contexts
 

javascript/packages/cli/README.md

@@ -177,7 +177,7 @@ Then you can spawn the network by running the following command:
 ❯ ./zombienet-macos spawn --provider native examples/0001-small-network.toml
 ```
 
-**Note:** before spawning network one needs to varify that `kubectl`'s namespace is set to `default`
+**Note:** before spawning network one needs to verify that `kubectl`'s namespace is set to `default`
 ```bash
 ❯ kubectl config get-contexts
 

javascript/packages/orchestrator/README.md

@@ -177,7 +177,7 @@ Then you can spawn the network by running the following command:
 ❯ ./zombienet-macos spawn --provider native examples/0001-small-network.toml
 ```
 
-**Note:** before spawning network one needs to varify that `kubectl`'s namespace is set to `default`
+**Note:** before spawning network one needs to verify that `kubectl`'s namespace is set to `default`
 ```bash
 ❯ kubectl config get-contexts
 

javascript/words.txt

@@ -171,7 +171,6 @@ unfollow
 unhandle
 unsub
 uutils
-varify
 webrtc
 westend
 westmint