diff options
| -rw-r--r-- | doc/spam.txt | 4 | ||||
| -rw-r--r-- | doc/tutorial.txt | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/doc/spam.txt b/doc/spam.txt index e201bf2..80a43ff 100644 --- a/doc/spam.txt +++ b/doc/spam.txt @@ -45,7 +45,7 @@ If the offending commit is not the last commit increment ``XYZ`` by hand for ``<XYZ+1>``, because ``bzr`` does not support ``after:XYZ``. -.. [#] From `Mercurial: The Definitive Guide`_: +.. [#] From `Mercurial, The Definitive Guide`_: "Mercurial also does not provide a way to make a file or changeset completely disappear from history, because there is no @@ -54,7 +54,7 @@ If the offending commit is not the last commit .. [#] See `Rebuilding ancestry`_ in the Monotone documentation. .. _bzr-rebase plugin: http://wiki.bazaar.canonical.com/Rebase -.. _Mercurial: The Definitive Guide: +.. _Mercurial, The Definitive Guide: http://hgbook.red-bean.com/read/finding-and-fixing-mistakes.html#id394667 .. _Rebuilding ancestry: http://www.monotone.ca/docs/Rebuilding-ancestry.html diff --git a/doc/tutorial.txt b/doc/tutorial.txt index 7b7220f..e6790cd 100644 --- a/doc/tutorial.txt +++ b/doc/tutorial.txt @@ -102,8 +102,8 @@ if you call it from a directory besides your project's root. Inside the ``.be`` directory (among other things) there will be a long UUID_ directory. This is your bug directory. The idea is that you could keep several bug directories in the same repository, using one -to track bugs, another to track roadmap issues, etc. See IDs_ for -details. For BE itself, the bug directory is +to track bugs, another to track roadmap issues, etc. See :mod:`IDs` +for details. For BE itself, the bug directory is ``bea86499-824e-4e77-b085-2d581fa9ccab``, which is why all the bug and comment IDs in this tutorial will start with ``bea/``. |