diff --git a/Documentation/dev-release-subproject.txt b/Documentation/dev-release-subproject.txt
index b0607fd..f686d0c 100644
--- a/Documentation/dev-release-subproject.txt
+++ b/Documentation/dev-release-subproject.txt
@@ -60,15 +60,15 @@
 
 * Deploy the snapshot:
 
-----
+====
   mvn deploy
-----
+====
 
 
 Making a Gerrit Subproject Release
 ----------------------------------
 
-* First deploy (and test) the latest snapshot for this subprojects
+* First deploy (and test) the latest snapshot for the subproject
 
 * Update the top level pom.xml in the subproject to reflect the new project
 version (the exact value of the tag you will create below)
@@ -77,8 +77,18 @@
 
 * Tag the version you just pushed (and push the tag)
 
+====
+ git tag -a -m "prolog-cafe 1.3" v1.3
+ git push gerrit-review refs/tags/v1.3:refs/tags/v1.3
+====
+
 * Deploy the new release:
 
-----
+====
  mvn deploy
-----
+====
+
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
diff --git a/Documentation/dev-release.txt b/Documentation/dev-release.txt
index 21dc1c7..0d07ba8 100644
--- a/Documentation/dev-release.txt
+++ b/Documentation/dev-release.txt
@@ -130,8 +130,8 @@
 * Push the New Tag
 
 ====
- git push google refs/tags/v2.5-rc0:refs/tags/v2.5-rc0
- git push google refs/tags/v2.5:refs/tags/v2.5
+ git push gerrit-review refs/tags/v2.5-rc0:refs/tags/v2.5-rc0
+ git push gerrit-review refs/tags/v2.5:refs/tags/v2.5
 ====
 
 
@@ -192,8 +192,7 @@
 Mailing List
 ~~~~~~~~~~~~
 
-* Send an email to the mailing list to announce the release
-* Consider including some or all of the following in the email:
+* Send an email to the mailing list to announce the release, consider including some or all of the following in the email:
 ** A link to the release and the release notes (if a final release)
 ** A link to the docs
 ** Describe the type of release (stable, bug fix, RC)
@@ -237,3 +236,8 @@
  git branch -f stable origin/stable
  git merge stable
 ====
+
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]