Additional fixes to the docs

Author: bladyjoker

docs/plutarch.md

@@ -41,7 +41,7 @@ For a full example see [Example](#example).
 
 ## LambdaBuffers modules
 
-Writing .lbf schemas with API types intended for Plutarch backend will typically use the following LambdaBuffers modules:
+Writing .lbf schemas with API types intended for Plutarch backend will typically use the following LambdaBuffers schema modules:
 
 1. [Prelude](../libs/lbf-prelude/Prelude.lbf),
 2. [Plutus.V1](../libs/lbf-plutus/Plutus/V1.lbf),
@@ -54,10 +54,10 @@ Take a look at [Example.lbf](./plutarch/api/Example.lbf) schema as an example.
 The necessary LambdaBuffers runtime libraries a typical Plutarch project needs when working with LambdaBuffers:
 
 1. [lbr-plutarch](../runtimes/haskell/lbr-plutarch) a Haskell runtime library necessary for working with `lbf-xyz` libraries.
-2. [lbf-prelude-plutarch](../libs/lbf-prelude) that contains the [LambdaBuffers Prelude](../libs/lbf-prelude) package generated by LambdaBuffers.
-3. [lbf-plutus-plutarch](../libs/lbf-plutus) that contains the [LambdaBuffers Plutus](../libs/lbf-plutus) package generated by LambdaBuffers.
+2. [lbf-prelude-plutarch](../libs/lbf-prelude) that contains the [LambdaBuffers Prelude](../libs/lbf-prelude) schema library generated by LambdaBuffers.
+3. [lbf-plutus-plutarch](../libs/lbf-plutus) that contains the [LambdaBuffers Plutus](../libs/lbf-plutus) schema library generated by LambdaBuffers.
 
-Of course, additionally imports for Plutarch libraries is also necessary [plutarch](https://github.com/Plutonomicon/plutarch-plutus) and optionally [plutarch-extra](https://github.com/Plutonomicon/plutarch-plutus/plutarch-extra).
+Of course, additional imports for Plutarch libraries are also necessary [plutarch](https://github.com/Plutonomicon/plutarch-plutus) and optionally [plutarch-extra](https://github.com/Plutonomicon/plutarch-plutus/plutarch-extra).
 
 For a full example see [Example](#example).
 
@@ -86,7 +86,7 @@ result/autogen/LambdaBuffers/Plutus/V1/Plutarch.hs
 
 ## Haskell modules
 
-The set of imports a Haskell module using LambdaBuffers modules would typically need is the following:
+The set of imports a Plutarch program using LambdaBuffers would typically need is the following:
 
 ```haskell
 import LambdaBuffers.Plutus.V1.Plutarch ()
@@ -153,9 +153,9 @@ The Plutarch backend doesn't support the use of `Char`, `Text`, `Bytes` (there's
 
 ### Type definition mapping
 
-Plutarch backend supports all types from the LambdaBuffers Plutus module, as to enable full featured Plutus script development.
+Plutarch backend supports all types from the [LambdaBuffers Plutus](../libs/lbf-plutus) schema library, as to enable full featured Plutus script development.
 
-Additionally, it also supports some types from the LambdaBuffers Prelude module, namely `Bool`, `Integer`, `Maybe`, `Either` and `List`.
+Additionally, it also supports some types from the [LambdaBuffers Prelude](../libs/lbf-prelude) schema library, namely `Bool`, `Integer`, `Maybe`, `Either` and `List`.
 
 ```lbf
 module Foo
@@ -310,7 +310,7 @@ infix 4 #==
 
 > We don't generate an implementation from the LambdaBuffers 'equality spec', rather we delegate the equality check to the underlying 'PData' representations that all generated types have for performance.
 
-### PShow
+#### PShow
 
 All generated types have a PShow instance derived using the internal Plutarch deriving mechanism.
 
@@ -322,7 +322,7 @@ Let work through the [Plutarch example](./plutarch) available in the repo.
 
 First, please check the [Getting started](getting-started.md) guide on how to prepare to work with the repo and setup Nix.
 
-### Directory contents
+Let's see what we have here:
 
 ```shell
 lambda-buffers/docs/plutarch ❯ find