docs: fix spelling issues (#2232)

docs/_templates/layout.html

@@ -61,7 +61,7 @@
     <script src="{{ pathto('_static/js/html5shiv.min.js', 1) }}"></script>
   <![endif]-->
   {%- if not embedded %}
-  {# XXX Sphinx 1.8.0 made this an external js-file, quick fix until we refactor the template to inherert more blocks directly from sphinx #}
+  {# XXX Sphinx 1.8.0 made this an external js-file, quick fix until we refactor the template to inherent more blocks directly from sphinx #}
     {%- if sphinx_version_info >= (1, 8) -%}
       {%- for scriptfile in script_files %}
         {{ js_tag(scriptfile) }}

docs/userguides/clis.md

@@ -74,7 +74,7 @@ To specify the network option, use values like:
 ```
 
 To use default values automatically, omit sections of the choice, but leave the semi-colons for parsing.
-For example, `::test` means use the default ecosystem and network and the `test` provider.
+For example, `::test` means to use the default ecosystem and network and the `test` provider.
 
 Use `ecosystem`, `network`, and `provider` argument names in your command implementation to access their corresponding class instances:
 

docs/userguides/console.md

@@ -137,7 +137,7 @@ Commands:
   cache     Query from caching database
   compile   Compile select contract source files
   console   Load the console
-  init      Initalize an ape project
+  init      Initialize an ape project
   networks  Manage networks
   plugins   Manage ape plugins
   run       Run scripts from the `scripts/` folder

docs/userguides/contracts.md

@@ -79,7 +79,7 @@ Simply copy your Python logic into an Ape script and run it via:
 ape run <my-deploy-script>
 ```
 
-Learn how to do this and scripting in its entirity by reviewing [the scripting user-guide](./scripts.html).
+Learn how to do this and scripting in its entirety by reviewing [the scripting user-guide](./scripts.html).
 
 **There is no root `ape` command to deploy contracts; only the scripting-system, the `console`, or merely using Ape as a Python library**.