web commit by JoshTriplett: Fix duplicated "moreinfo" tag.

[ikiwiki.git] / doc / tips / issue_tracking.mdwn

diff --git a/doc/tips/issue_tracking.mdwn b/doc/tips/issue_tracking.mdwn
index 20866f0debbaee7832d8e2a5deb0191517ea32c6..28f7ba7a16a9491c5a6a693e24afbf97532fed21 100644 (file)
--- a/doc/tips/issue_tracking.mdwn
+++ b/doc/tips/issue_tracking.mdwn
@@ -18,7 +18,7 @@ described by the term "wiki compiler". Just as a
 typical software project consists of source code
 that is stored in revision control and compiled with
 `make` and `gcc`, an ikiwiki-based wiki is stored as
 typical software project consists of source code
 that is stored in revision control and compiled with
 `make` and `gcc`, an ikiwiki-based wiki is stored as

-human editable source in a revision control system,
+human-editable source in a revision control system,

 and built into HTML using ikiwiki.
 
 Ikiwiki uses your revision control system to track
 and built into HTML using ikiwiki.
 
 Ikiwiki uses your revision control system to track


@@ -40,7 +40,7 @@ Ikiwiki is a full-featured wiki that you can use
 for a variety of purposes, from traditional wikis
 to weblogs, podcasting, or even aggregating other
 sites' RSS feeds into a Planet page. While people
 for a variety of purposes, from traditional wikis
 to weblogs, podcasting, or even aggregating other
 sites' RSS feeds into a Planet page. While people

-are [[using|ikiwikiusers.html]]
+are [[using|ikiwikiusers]]

 Ikiwiki for purposes ranging from genealogy research
 to shoe accessory sales, one thing it's especially
 well suited for is collaborative software development,
 Ikiwiki for purposes ranging from genealogy research
 to shoe accessory sales, one thing it's especially
 well suited for is collaborative software development,


@@ -54,7 +54,8 @@ The simplest way to use ikiwiki is to build static
 HTML files from source wiki files. This example builds
 a wiki for an imaginary software project.  The wiki
 source files used in this example are available in the
 HTML files from source wiki files. This example builds
 a wiki for an imaginary software project.  The wiki
 source files used in this example are available in the

-[[examples/softwaresite]] section of ikiwiki's documentation.
+[[examples/softwaresite|examples/softwaresite]] section
+of ikiwiki's documentation.

 
        wiki$ ls
        Makefile  bugs.mdwn     doc/      download.mdwn  news/
 
        wiki$ ls
        Makefile  bugs.mdwn     doc/      download.mdwn  news/


@@ -128,8 +129,8 @@ While directories are useful for broad hierarchical
 grouping, tags are better for categorizing issues
 as bugs, wishlist items, security issues, patches,
 or whatever other categories are useful. Bugs can
 grouping, tags are better for categorizing issues
 as bugs, wishlist items, security issues, patches,
 or whatever other categories are useful. Bugs can

-be tagged "moreinfo", "done" "unreproducible",
-or "moreinfo", etc, to document different stages of
+be tagged "moreinfo", "done", "unreproducible",
+etc, to document different stages of

 their lifecycle. A developer can take ownership of a
 bug by tagging it with something like "owner/Joey".
 
 their lifecycle. A developer can take ownership of a
 bug by tagging it with something like "owner/Joey".