Merge pull request #143 from mathstuf/tagging-rewording

Tagging rewording

Author: dtolnay

src/documentation.md

@@ -255,23 +255,26 @@ is located at `"https://api.rocket.rs/rocket/index.html"` then the
 ## Release notes document all significant changes (C-RELNOTES)
 
 Users of the crate can read the release notes to find a summary of what
-changed in each published release of the crate.  A link to the release notes,
+changed in each published release of the crate. A link to the release notes,
 or the notes themselves, should be included in the crate-level documentation
 and/or the repository linked in Cargo.toml.
 
 Breaking changes (as defined in [RFC 1105]) should be clearly identified in the
 release notes.
 
-If using git to track the source of a crate, every release published to
-*crates.io* should have a corresponding git tag identifying the commit that was
-published. A similar process should exist for non-git VCS tools as well.
+If using Git to track the source of a crate, every release published to
+*crates.io* should have a corresponding tag identifying the commit that was
+published. A similar process should be used for non-Git VCS tools as well.
 
 ```bash
 # Tag the current commit
-GIT_COMMITTER_DATE=$(git show --format=%aD | head -1) git tag -a -m "Release 0.3.0" 0.3.0
+GIT_COMMITTER_DATE=$(git log -n1 --pretty=%aD) git tag -a -m "Release 0.3.0" 0.3.0
 git push --tags
 ```
 
+Annotated tags are preferred because some Git commands ignore unannotated tags
+if any annotated tags exist.
+
 [RFC 1105]: https://github.com/rust-lang/rfcs/blob/master/text/1105-api-evolution.md
 
 ### Examples