Trim verbose examples

doc/5.x-final.md

@@ -60,17 +60,7 @@ If this branch will have future ESR support, then you should also publish releas
 releaser -v gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json get sign tag publish esr-tag esr-publish
 ```
 
-Note: You may run tasks individually, and you may do dry-runs (`--dry-run`/`-N`). For example
-
-```
-cd ~/src/master
-
-## Publish tarballs to Google Cloud and Sourceforge (dry run)
-releaser -v gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json publish -N
-
-## Publish tarballs to Google Cloud and Sourceforge (really)
-releaser -v gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json publish
-```
+> TIP: `releaser` can run steps individually, and it can provide a preview of actions it would take (`--dry-run` aka `-N`).
 
 To ensure the various tags were published and match the branches, use `civi-git-table`, as in:
 

doc/5.x-patch.md

@@ -97,17 +97,7 @@ If this branch will have future ESR support, then you should also publish releas
 releaser -v gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json get sign tag publish esr-tag esr-publish
 ```
 
-Note: You may run tasks individually, and you may do dry-runs (`--dry-run`/`-N`). For example
-
-```
-cd ~/src/master
-
-## Publish tarballs to Google Cloud and Sourceforge (dry run)
-releaser -v gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json publish -N
-
-## Publish tarballs to Google Cloud and Sourceforge (really)
-releaser -v gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json publish
-```
+> TIP: `releaser` can run steps individually, and it can provide a preview of actions it would take (`--dry-run` aka `-N`).
 
 To ensure the various tags were published and match the branches, use `civi-git-table`, as in: