aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorW. Trevor King <wking@drexel.edu>2011-05-11 17:57:24 -0400
committerW. Trevor King <wking@drexel.edu>2011-05-11 17:57:24 -0400
commit463e44ac93834de237d71ffb1fdd490a649b59aa (patch)
tree2b119f093b89d092b8db8c78e1d039898c54b08c /doc
parent51d7cc3725131e247e9ac207b7dbb4cc2bcd5123 (diff)
downloadbugseverywhere-463e44ac93834de237d71ffb1fdd490a649b59aa.tar.gz
Fix links to libbe.util.id from doc/tutorial.txt.
Diffstat (limited to 'doc')
-rw-r--r--doc/tutorial.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/tutorial.txt b/doc/tutorial.txt
index e6790cd..c82f7c5 100644
--- a/doc/tutorial.txt
+++ b/doc/tutorial.txt
@@ -16,7 +16,7 @@ and helps keep the bug repository in sync with the code.
However, there are some differences compared to centralized
bugtrackers. Because bugs and comments can be created by several
users in parallel, they have globally unique :mod:`IDs
-</libbe.util.id>` rather than numbers. There is also a
+<libbe.util.id>` rather than numbers. There is also a
developer-friendly command-line_ interface to compliment the
user-friendly :doc:`web </http>` and :doc:`email </email>` interfaces.
This tutorial will focus on the command-line interface as the most
@@ -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 :mod:`IDs`
-for details. For BE itself, the bug directory is
+to track bugs, another to track roadmap issues, etc. See :mod:`IDs
+<libbe.util.id>` 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/``.