Docs: fix typos

docs/compiling-a-contract.rst

@@ -92,7 +92,7 @@ Importing Interfaces
 
 1. Interfaces defined in the ``interfaces`` field of the input JSON.
 2. Derived interfaces generated from contracts in the ``sources`` field of the input JSON.
-3. (Optional) The local filesystem, if a root path was explicitely declared via the ``-p`` flag.
+3. (Optional) The local filesystem, if a root path was explicitly declared via the ``-p`` flag.
 
 See :ref:`searching_for_imports` for more information on Vyper's import system.
 

docs/control-structures.rst

@@ -222,7 +222,7 @@ The ``for`` statement is a control flow construct used to iterate over a value:
     for i in <ITERABLE>:
         ...
 
-The iterated value can be a static array, or generated from the builtin ``range`` function.
+The iterated value can be a static array, or generated from the built-in ``range`` function.
 
 Array Iteration
 ---------------

docs/interfaces.rst

@@ -145,7 +145,7 @@ Searching For Interface Files
 
 When looking for a file to import, Vyper will first search relative to the same folder as the contract being compiled. For absolute imports, it also searches relative to the root path for the project. Vyper checks for the file name with a ``.vy`` suffix first, then ``.json``.
 
-When using the command line compiler, the root path defaults to to the current working directory. You can change it with the ``-p`` flag:
+When using the command line compiler, the root path defaults to the current working directory. You can change it with the ``-p`` flag:
 
 ::