KnowledgeBase/Versions-and-Tag-Management.md

@@ -40,7 +40,7 @@ When working with agile sprints, we typically have a new `-pre#` tag per each sp
 
 # `bump2version`
 
-`bump2version` (or just `bumpversion`, the terms are synonims) is small command line tool written in python to simplify releasing software by updating all version strings in your source code by the correct increment. 
+`bump2version` (or just `bumpversion`, the terms are synonyms) is small command line tool written in python to simplify releasing software by updating all version strings in your source code by the correct increment. 
 
 Also creates commits and tags
 
@@ -52,7 +52,7 @@ Waf and ELT DevEnv provide some support, and more will be probably added in the
 
 - The `.bumpversion.cfg` file contains the configuration for the `bumpversion` command
 - This file shall appear in the the root folder of a project
-- *Note:* The file is automatically overwritten every time the `bumpversion` command is executed. Therefore, do not change it by hand and do not put there comments, as they will be removed at the next ececution.
+- *Note:* The file is automatically overwritten every time the `bumpversion` command is executed. Therefore, do not change it by hand and do not put there comments, as they will be removed at the next execution.
 
 What follows is an example of `.bumpversion.cfg` file, with additional comments.
 For details on the syntax see: https://github.com/c4urself/bump2version
@@ -176,7 +176,7 @@ The following is an example of a final release with manually specified version:
 
     $ bump2version --tag --message="Release v{new_version}" --new-version="x.y.z"
 
-# Files contianing version information to be replaced by `bump2version`
+# Files containing version information to be replaced by `bump2version`
 
 ## `.version` file