diff --git a/docs/composer-cli.rst b/docs/composer-cli.rst
index 7cde6feb..366e01ad 100644
--- a/docs/composer-cli.rst
+++ b/docs/composer-cli.rst
@@ -27,7 +27,7 @@ blueprints save http-server``. If there are no blueprints available you can
 copy one of the examples `from the test suite
 <https://github.com/weldr/lorax/tree/master/tests/pylorax/blueprints/>`_.
 
-Edit the file (it will be saved with a .toml extension) and chance the
+Edit the file (it will be saved with a .toml extension) and change the
 description, add a package or module to it. Send it back to the server by
 running ``composer-cli blueprints push http-server.toml``. You can verify that it was
 saved by viewing the changelog - ``composer-cli blueprints changes http-server``.
diff --git a/docs/lorax-composer.rst b/docs/lorax-composer.rst
index 9fc3b229..b107073d 100644
--- a/docs/lorax-composer.rst
+++ b/docs/lorax-composer.rst
@@ -120,7 +120,9 @@ when it is written to disk. It should be short and descriptive.
 ``version`` is a `semver compatible <https://semver.org/>`_ version number. If
 a new blueprint is uploaded with the same ``version`` the server will
 automatically bump the PATCH level of the ``version``. If the ``version``
-doesn't match it will be used as is. eg. Uploading a blueprint with ``version`` set to ``0.0.1`` when the existing blueprint ``version`` is ``0.0.1`` will result in the new blueprint being stored as ``version 0.0.1``.
+doesn't match it will be used as is. eg. Uploading a blueprint with ``version``
+set to ``0.1.0`` when the existing blueprint ``version`` is ``0.0.1`` will
+result in the new blueprint being stored as ``version 0.1.0``.
 
 [[packages]] and [[modules]]
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~