diff --git a/README.rst b/README.rst
index bea57ba..4e9be8b 100644
--- a/README.rst
+++ b/README.rst
@@ -26,7 +26,7 @@ Usage
 DB Setup
 --------
 
-The usage of subunit2ql is split into 2 stages. First you need to prepare a
+The usage of subunit2sql is split into 2 stages. First you need to prepare a
 database with the proper schema; subunit2sql-db-manage should be used to do
 this. The utility requires db connection info which can be specified on the
 command or with a config file. Obviously the sql connector type, user,
diff --git a/subunit2sql/db/api.py b/subunit2sql/db/api.py
index e7b0935..565cef3 100644
--- a/subunit2sql/db/api.py
+++ b/subunit2sql/db/api.py
@@ -80,7 +80,7 @@ def create_run(skips=0, fails=0, passes=0, run_time=0, artifacts=None,
                session=None):
     """Create a new run record in the database
 
-    :param skips: total number of skiped tests
+    :param skips: total number of skipped tests
     :param fails: total number of failed tests
     :param passes: total number of passed tests
     :param run_time: total run time
diff --git a/subunit2sql/read_subunit.py b/subunit2sql/read_subunit.py
index 4e47777..f16508f 100644
--- a/subunit2sql/read_subunit.py
+++ b/subunit2sql/read_subunit.py
@@ -62,7 +62,7 @@ class ReadSubunit(object):
             metadata['attrs'] = attrs
         if test['tags']:
             metadata['tags'] = test['tags']
-        # Return code is a a fail don't process it
+        # Return code is a fail don't process it
         if name == 'process-returncode':
             return
         timestamps = test['timestamps']
@@ -90,7 +90,7 @@ class ReadSubunit(object):
 
         Make it possible to strip out the testscenarios information (not to
         be confused with tempest scenarios) however that's often needed to
-        indentify generated negative tests.
+        identify generated negative tests.
         """
         if strip_tags:
             tags_start = name.find('[')