Merge pull request #71 from 1Maxnet1/readme-improvements

Fix typos in README.rst

Author: fpurcell

README.rst

@@ -30,7 +30,7 @@ Install from source via github (if you want the latest code) :
 
 #. Install Python 3.x https://www.python.org/downloads/ (code also runs on 2.7 if you are stuck on that version)
 #.  `pip install zc.buildout` - https://pypi.org/project/zc.buildout
-#. (optinal step for **postgres users**: 'pip install psycopg2-binary')
+#. (optional step for **postgres users**: 'pip install psycopg2-binary')
 #. git clone https://github.com/OpenTransitTools/gtfsdb.git
 #. cd gtfsdb
 #. buildout install prod -- NOTE: if you're using postgres, do a 'buildout install prod postgresql'
@@ -43,16 +43,16 @@ Install from source via github (if you want the latest code) :
 
    * bin/gtfsdb-load --database_url postgresql://postgres@localhost:5432 --is_geospatial http://developer.trimet.org/schedule/gtfs.zip
 
-     .. note:: adding the `is_geospatial` cmdline flag, when paired with a spatial-database ala PostGIS (e.g., is_spatial is meaningless with sqllite), will take longer to load...but will create geometry columns for both rendering and calculating nearest distances, etc...
+     .. note:: adding the `is_geospatial` cmdline flag, when paired with a spatial-database ala PostGIS (e.g., is_spatial is meaningless with sqlite), will take longer to load...but will create geometry columns for both rendering and calculating nearest distances, etc...
 
 #. view db ( example: https://sqliteonline.com )
 
 The best way to get gtfsdb up and running is via the 'zc.buildout' tool.  Highly recommended to first install
 buildout (e.g., pip install zc.buildout) before doing much of anything else.
 
-Postgres users, gtfsdb requires the psycopg2-binary database driver.  Installing that via `pip install psychopg2-binary` will relieve gtfsdb from re-installing locally as part of the build.  And if after the fact, you see *exceptions* mentioning
+Postgres users, gtfsdb requires the psycopg2-binary database driver.  Installing that via `pip install psycopg2-binary` will relieve gtfsdb from re-installing locally as part of the build.  And if after the fact, you see *exceptions* mentioning
 
-.. note:: if you get the message "ImportError: No module named psycopg2", then 'pip install psychopg2-binary' should fix things. (Assumes you have postgres also installed on the machine you're trying to use the pg driver).
+.. note:: if you get the message "ImportError: No module named psycopg2", then 'pip install psycopg2-binary' should fix things. (Assumes you have postgres also installed on the machine you're trying to use the pg driver).
 
 
 Usage with Docker: