@ teracyhq#363 | should update releases/vX.X.X convention: feedbacks …

…applied
hoatle · Jul 20, 2017 · 3ce5f41 · 3ce5f41
1 parent b8e9649
commit 3ce5f41
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/docs/release_process.rst b/docs/release_process.rst
@@ -6,12 +6,12 @@ This is the general guide for releasing software packages at Teracy.
 Starting
 --------
 
-- Follow workflow, a releasing branch should be branched off from origin branch that is ready to be
+- Follow workflow, a releasing branch should be branched off from an origin branch that is ready to be
   released.
 
 - The releasing branch should be named ``releases/vX.X.X``.
 
-- For example: ``releases/v0.1.0`` branch is branched off from the ``develop`` branch.
+- For example: the ``releases/v0.1.0`` branch is branched off from the ``develop`` branch.
 
 - Set the next iteration version for the ``develop`` branch. This will make sure there is no snapshot
   version conflict between the ``releases`` branch and the ``develop`` branch. Moreover, the
@@ -29,7 +29,7 @@ Releasing
 
 - Remember that release branch should not introduce big changes.
 
-- After each staging releases, create an issue for release test campaign to make sure the release
+- After each staging release, create an issue for release test campaign to make sure the release
   is stable enough and have good quality.
 
 Ending
@@ -45,7 +45,7 @@ Ending
 - Merge the tag release into the ``master`` branch, then the origin branch. This is specified on the
   project workflow.
 
-- Delete released branch and we are done.
+- Delete the released branch and we are done.
 
 .. note::