Fixed typos

README.md

@@ -18,7 +18,7 @@ never had a *year zero*).
 
 ## Versioning
 
-pgloader version 1.x is quite old and was devleoped in `TCL`.
+pgloader version 1.x is quite old and was developed in `TCL`.
 When faced with maintaining that code, the new emerging development
 team (hi!) picked `python` instead because that made sense at the
 time. So pgloader version 2.x was written in python.

TODO.md

@@ -80,12 +80,12 @@ simpler.
 ### performances
 
   - some more parallelizing options
-  - support for partitionning in pgloader itself
+  - support for partitioning in pgloader itself
 
 ### UI
 
-  - add a web controler with pretty monitoring
-  - launch new jobs from the web controler
+  - add a web controller with pretty monitoring
+  - launch new jobs from the web controller
 
 ### crazy ideas
 

src/connection.lisp

@@ -1,5 +1,5 @@
 ;;
-;; Abstrat classes to define the API to connect to a data source
+;; Abstract classes to define the API to connect to a data source
 ;;
 (in-package :pgloader.connection)
 

src/sources/mssql/mssql.lisp

@@ -262,7 +262,7 @@
 
           (return-from copy-database)))
 
-      ;; Transfert the data
+      ;; Transfer the data
       (loop :for (schema . tables) :in all-columns
          :do (loop :for (table-name . columns) :in tables
                 :do

web/src/geolite.md

@@ -104,7 +104,7 @@ The transformation from a pair of integers into an IP is done dynamically by
 the pgloader process.
 
 Also, the location is given as a pair of *float* columns for the *longitude*
-and the *latiude* where PostgreSQL offers the
+and the *latitude* where PostgreSQL offers the
 [point](http://www.postgresql.org/docs/9.3/interactive/functions-geometry.html)
 datatype, so the pgloader command here will actually transform the data on
 the fly to use the appropriate data type and its input representation.