diff --git a/docs/introduction/install.md b/docs/introduction/install.md
index f7d78aba..f3498514 100644
--- a/docs/introduction/install.md
+++ b/docs/introduction/install.md
@@ -95,9 +95,9 @@ wget https://github.com/google/leveldb/archive/v1.20.tar.gz && \
   tar -zxvf v1.20.tar.gz && \
   cd leveldb-1.20/ && \
   make && \
-  sudo scp -r out-static/lib* out-shared/lib* /usr/local/lib/ && \
+  cp -r out-static/lib* out-shared/lib* /usr/local/lib/ && \
   cd include/ && \
-  sudo scp -r leveldb /usr/local/include/ && \
+  cp -r leveldb /usr/local/include/ && \
   sudo ldconfig && \
   rm -f v1.20.tar.gz
 ```
diff --git a/docs/spec/abci/apps.md b/docs/spec/abci/apps.md
index 0e8057b5..a8f37771 100644
--- a/docs/spec/abci/apps.md
+++ b/docs/spec/abci/apps.md
@@ -95,7 +95,7 @@ The `Data` field must be strictly deterministic, but can be arbitrary data.
 
 ### Gas
 
-Ethereum introduced the notion of `gas` as an absract representation of the
+Ethereum introduced the notion of `gas` as an abstract representation of the
 cost of resources used by nodes when processing transactions. Every operation in the
 Ethereum Virtual Machine uses some amount of gas, and gas can be accepted at a market-variable price.
 Users propose a maximum amount of gas for their transaction; if the tx uses less, they get
@@ -123,7 +123,7 @@ Note that Tendermint does not currently enforce anything about Gas in the consen
 This means it does not guarantee that committed blocks satisfy these rules!
 It is the application's responsibility to return non-zero response codes when gas limits are exceeded.
 
-The `GasUsed` field is ignored compltely by Tendermint. That said, applications should enforce:
+The `GasUsed` field is ignored completely by Tendermint. That said, applications should enforce:
 
 - `GasUsed <= GasWanted` for any given transaction
 - `(sum of GasUsed in a block) <= MaxGas` for every block
diff --git a/docs/tendermint-core/running-in-production.md b/docs/tendermint-core/running-in-production.md
index bdb824d6..c774cd13 100644
--- a/docs/tendermint-core/running-in-production.md
+++ b/docs/tendermint-core/running-in-production.md
@@ -5,7 +5,7 @@
 By default, Tendermint uses the `syndtr/goleveldb` package for it's in-process
 key-value database. Unfortunately, this implementation of LevelDB seems to suffer under heavy load (see
 [#226](https://github.com/syndtr/goleveldb/issues/226)). It may be best to
-install the real C-implementaiton of LevelDB and compile Tendermint to use
+install the real C-implementation of LevelDB and compile Tendermint to use
 that using `make build_c`. See the [install instructions](../introduction/install.md) for details.
 
 Tendermint keeps multiple distinct LevelDB databases in the `$TMROOT/data`: