diff --git a/Development-process.md b/Development-process.md
index 078f59b..63af5bd 100644
--- a/Development-process.md
+++ b/Development-process.md
@@ -1,4 +1,4 @@
-There as many different ways of developing software for single-board computers, such as the Raspberry Pi, as there are developers who do it. Likewise, opinions vary as to which approach is best. Ultimately it's the process that works for best for _you_ that prevails. This briefly describes two approaches used by contributors to RaspAP. 
+There are as many different ways of developing software for single-board computers, such as the Raspberry Pi, as there are developers who do it. Likewise, opinions vary as to which approach is best. Ultimately it's the process that works for best for _you_ that prevails. This briefly describes two approaches used by contributors to RaspAP. 
 
 ## Remote host update
 Project contributor [@glaszig](https://github.com/glaszig) maintains a working copy of RaspAP on his workstation and automatically copies changes over to the Pi. He has written [this handy script](https://gist.github.com/glaszig/673691a6ba7bdc8e3d054d826a179976) to automate the process by way of `fswatch`. The script watches a local (dev) directory and pushes changes to the remote target (the Pi, in this case) via SCP, or secure copy. This way, you can use the Integrated Development Environment (IDE) of your choosing and simply push updates in the background to a remote system. More on fswatch [here](http://emcrisostomo.github.io/fswatch/).