fix: typos (#14)

Author: olebedev

docs/usage.md

@@ -44,7 +44,7 @@ Then, import this expression by changing the file above with the following:
 This `js2nix.buildEnv` (or simply `js2nix`) is the main functionality js2nix provides as its API, however, there are a couple more function that are also exposed for more granular advanced use-cases (see the [`../lib.nix`](../lib.nix) for more information).
 
 This function accepts the following arguments:
-- `package-json` - a path to a `pacakge.json` file.
+- `package-json` - a path to a `package.json` file.
 - `yarn-lock` - a path to a `yarn.lock` file, or
 - `yarn-lock-nix` - a path to a file that was generated by the `js2nix` executable directly from `yarn.lock` file. Used to avoid IFD situation, where needed.
 - `overlays` - a list of overlay functions to override the dependency tree, see [overiding](#overiding) section below for more details.
@@ -60,8 +60,8 @@ The function returns an environment object that consists of the following:
   ```nix
   self: super: {
     # represents a package derivation by direct name with a version
-    "[email protected]" = buildNodeModiule { 
-      # ... a pacakge build logic, internal js2nix implementation
+    "[email protected]" = self.buildNodeModule { 
+      # ... a package build logic, internal js2nix implementation
     };
     "yargs@^16.0.3" = self."[email protected]";
     "yargs" = self."[email protected]";
@@ -166,7 +166,7 @@ let
 in env
 ```
 
-Due to yarn not providing information about peer dependencies within the `yarn.lock` file, it's only possible to make packages with peer dependencies work by overriding their dependencies and providing them as in the example above. Norre that defining those dependencies on the top-level (in the `package.json` file) won't address this peer dependencies due to the nested [node_modules structure](#the-node_modules-folder-layout) that js2nix provides.
+Due to yarn not providing information about peer dependencies within the `yarn.lock` file, it's only possible to make packages with peer dependencies work by overriding their dependencies and providing them as in the example above. Note that defining those dependencies on the top-level (in the `package.json` file) won't address this peer dependencies due to the nested [node_modules structure](#the-node_modules-folder-layout) that js2nix provides.
 
 #### Basic overrides in `package.json` file
 
@@ -226,7 +226,7 @@ the same can be done in `package.json` file:
 ##### Supported overlay directives:
 - `js2nix.overlay.<package>.addDependencies` - list of strings. Can be an alias or a direct name with version, for example can be `"@babel/core"` or `"@babel/core@^7.1.0"` or `"@babel/[email protected]"`.
 - `js2nix.overlay.<package>.src` - string or an object. Overrides a package source. It can be a local folder path, relative to the `package.json` file or an absolute path. Also can be an object that overrides the `fetchurl` function attributes.
-- `js2nix.overlay.<package>.doCheck` - boolean. Overrides the `doCheck` argument for the pacakge builder. It's `true` by default.
+- `js2nix.overlay.<package>.doCheck` - boolean. Overrides the `doCheck` argument for the package builder. It's `true` by default.
 - `js2nix.overlay.<package>.patches` - a list of strings. Overrides patches with the given list. Items in the list can be strings that represent a path to a patch file, an absolute or relative the `package.json` file.
 - `js2nix.overlay.<package>.lifeCycleScripts` - a list of strings. Overrides `lifeCycleScripts`, can contains scripts' names, declared in the `package.json` of the package. TIP: you can use patch feature to add some scripts you need there.
 

overlay.nix

@@ -27,7 +27,7 @@ let
 in
 {
   # This is the entry point function that iterates over all the declarations in
-  # the `overlay` section in the `pacakge.json` file and invoke functions declared
+  # the `overlay` section in the `package.json` file and invoke functions declared
   # in this attr set.
   # 
   # Functions' naming convention: