Fixup and improve book using_modules.md

book/modules/using_modules.md

@@ -25,7 +25,7 @@ The example above uses the [Standard Library](../standard_library.md), a collect
 
 ## Installing Modules
 
-Installing a module is simply a matter of placing its files in a directory. This might be done via `git clone` (or other version control system), a package manager such as `nupm`, or manually. The module's documentation should provide recommendations.
+Installing a module is a matter of placing its files in a directory. This might be done via `git clone` (or other version control system), a package manager such as `nupm`, or manually. The module's documentation should provide recommendations.
 
 ## Importing Modules
 
@@ -42,7 +42,7 @@ The module's documentation will usually tell you the recommended way to import i
 
 The path to the module can be:
 
-- An absolute or relative path to a directory containing a `mod.nu` file:
+- An absolute path to a directory containing a `mod.nu` file:
 
   ::: details Example
 
@@ -69,25 +69,39 @@ The path to the module can be:
   Note that the module name (its directory) can end in a `/` (or `\` on Windows), but as with most commands that take a paths (e.g., `cd`), this is completely optional.
   :::
 
-  ::: important Important! Importing modules from `$env.NU_LIB_PATH`
+  ::: important Important! Importing modules from `$env.NU_LIB_DIRS`
   When importing a module via a relative path, Nushell first searches from the current directory. If a matching module is not found at that location, Nushell then searches each directory in the `$env.NU_LIB_DIRS` list.
 
   This allows you to install modules to a location that is easily accessible via a relative path regardless of the current directory.
   :::
 
-- An absolute or relative path to a Nushell module file. As above, Nushell will search the `$env.NU_LIB_DIRS` for a matching relative path.
+- An absolute path to a Nushell module file:
 
   ::: details Example
 
   ```nu
   use ~/nushell/modules/std-rfc/bulk-rename.nu
-  # Or
+  ```
+
+  :::
+
+- A relative path to a Nushell module file:
+
+  ::: details Example
+
+  ```nu
   cd ~/nushell/modules
   use std-rfc/bulk-rename.nu
   ```
 
   :::
 
+  ::: important Important! Importing modules from `$env.NU_LIB_DIRS`
+  When importing a module via a relative path, Nushell first searches from the current directory. If a matching module is not found at that location, Nushell then searches each directory in the `$env.NU_LIB_DIRS` list.
+
+  This allows you to install modules to a location that is easily accessible via a relative path regardless of the current directory.
+  :::
+
 - A virtual directory:
 
   ::: details Example
@@ -100,7 +114,7 @@ The path to the module can be:
 
   :::
 
-- Less commonly, the name of a module already created with the [`module`](/commands/docs/module.md) command. While it is possible to use this command to create a module at the commandline, this isn't common or useful. Instead, this form is primarily used by module authors to define a submodule. See [Creating Modules - Submodules](./creating_modules.md#submodules).
+- Less commonly, the name of a module is created with the [`module`](/commands/docs/module.md) command. While it is possible to use this command to create a module at the commandline, this isn't common or useful. Instead, this form is primarily used by module authors to define a submodule. See [Creating Modules - Submodules](./creating_modules.md#submodules).
 
 ### Module Definitions
 
@@ -193,7 +207,7 @@ assert true
 # => Assertion passes
 
 hide assert
-assert equal 1 1
+assert equal 1 2
 # => Error:
 # => help: A command with that name exists in module `assert`. Try importing it with `use`
 
@@ -208,7 +222,7 @@ Just as you can `use` a subset of the module's definitions, you can also `hide`
 ```nu
 use std/assert
 hide assert main
-assert equal 1 1
+assert equal 1 2
 # => assertion passes
 
 assert true
@@ -217,11 +231,11 @@ assert true
 ```
 
 ::: tip
-`main` is covered in more detail in [Creating Modules](./creating_modules.md#main-exports), but for end-users, `main` simply means "the command named the same as the module." In this case the `assert` module exports a `main` command that "masquerades" as the `assert` command. Hiding `main` has the effect of hiding the `assert` command, but not its subcommands.
+`main` is covered in more detail in [Creating Modules](./creating_modules.md#main-exports), but for end-users, `main` means "the command named the same as the module." In this case the `assert` module exports a `main` command that "masquerades" as the `assert` command. Hiding `main` has the effect of hiding the `assert` command, but not its subcommands.
 :::
 
 ## See Also
 
-- To make a module always be available without having to `use` it in each Nushell session, simply add its import (`use`) to your startup configuration. See the [Configuration](../configuration.md) Chapter to learn how.
+- To make a module always be available without having to `use` it in each Nushell session, add its import (`use`) to your startup configuration. See the [Configuration](../configuration.md) Chapter to learn how.
 
 - Modules can also be used as part of an [Overlay](../overlays.md).