Update 4.6-final.md

Use fewer words

doc/4.6-final.md

@@ -36,40 +36,28 @@ or do the steps individually:
 ```
 cd /path/to/civicrm
 
-## Get the RC tarballs
+## Download and rename the RC tarballs
 releaser gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json --get
 
 ## Generate signatures for tarballs
 releaser gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json --sign
 
-## Generate tags (dry run)
+## Generate tags in each repo (dry run)
 releaser gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json --tag -n
 
-## Publish tarballs (dry run)
+## Publish tarballs to Sourceforge and Gcloud (dry run)
 releaser gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json --publish -n
 
-## Tag (really)
+## Generate tags in each repo  (really)
 releaser gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json --tag -f
 
-## Publish (really)
+## Publish tarballs to Sourceforge and Gcloud (really)
 releaser gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json --publish
 ```
 
-Internally, these commands will:
- * Copy and rename the build artifacts for `civicrm-4.6.28-*201705030600*`
- * Generate and sign the MD5SUMS
- * Push `git` tags in each repo
-   * Fetch each `git` repo
-   * Determine the `git` commits used in this build
-   * Create tags for each repo
-   * Push tags for each repo
- * Publish the tarballs through the primary, long-term distribution channels
-   * Copy the corresponding tarballs to Google Cloud
-   * Copy the corresponding tarballs to Sourceforge
-
 ## Set default on `civicrm.org` (WIP)
 
-... updating versions.json...
+... login to `latest` and update versions.json ...
 
 ## Bump version