FIX: typo

pyscaffold · Jan 2, 2015 · f7bb81d · f7bb81d
1 parent 4b4f2b8
commit f7bb81d
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/README.rst b/README.rst
@@ -125,5 +125,5 @@ Keep your project's scaffold up-to-date by applying
 An update will only overwrite files that are not often altered by users like
 setup.py, versioneer.py etc. To update all files use ``--update --force``.
 An existing project that was not setup with PyScaffold can be converted with
-``putup --force existing_project``. The force option is completely save to use
+``putup --force existing_project``. The force option is completely safe to use
 since the git repository of the existing project is not touched!
diff --git a/docs/features.rst b/docs/features.rst
@@ -130,5 +130,5 @@ Keep your project's scaffold up-to-date by applying
 An update will only overwrite files that are not often altered by users like
 setup.py, versioneer.py etc. To update all files use ``--update --force``.
 An existing project that was not setup with PyScaffold can be converted with
-``putup --force existing_project``. The force option is completely save to use
+``putup --force existing_project``. The force option is completely safe to use
 since the git repository of the existing project is not touched!
diff --git a/pyscaffold/data/readme.template b/pyscaffold/data/readme.template
@@ -105,7 +105,7 @@ Keep your project's scaffold up-to-date by applying
 An update will only overwrite files that are not often altered by users like
 setup.py, versioneer.py etc. To update all files use ``--update --force``.
 An existing project that was not setup with PyScaffold can be converted with
-``putup --force existing_project``. The force option is completely save to use
+``putup --force existing_project``. The force option is completely safe to use
 since the git repository of the existing project is not touched!