Fossil

Check-in [6a5d3bb0]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Fixed a typo in documentation (closes ticket [1f82e0e1e])
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1:6a5d3bb089576dcd7eca9415edebf5875a6af05a
User & Date: BM 2011-01-26 12:02:51
Context
2011-01-26
15:37
Make the definition of "leaf" on the "leaves" page more precise. check-in: 752895d9 user: drh tags: trunk
12:02
Fixed a typo in documentation (closes ticket [1f82e0e1e]) check-in: 6a5d3bb0 user: BM tags: trunk
08:58
fixed a typo in webui.wiki check-in: ef80fd87 user: BM tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to www/wikitheory.wiki.

64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
Some project prefer to store their documentation in wiki.  There is nothing
wrong with that.  But other projects prefer to keep documentation as part
of the source tree, so that it is versioned along with the source tree and
so that only developers with check-in privileges can change it.  
Embedded documentation serves this latter purpose.  Both forms of documentation
use the exact same wiki markup language.  Some projects may choose to
use both forms of documentation at the same time.  Because the same
format is used, it is trivial to move file from wiki to embedded documentation
or back again as the project evolves.

<h2>Bug-reports and check-in comments</h2>

The comments on check-ins and the text in the descriptions of bug reports
both use wiki formatting.  Exactly the same set of formatting rules apply.
There is never a need to learn one formatting language for documentation
and a different markup for bugs or for check-in comments.







|








64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
Some project prefer to store their documentation in wiki.  There is nothing
wrong with that.  But other projects prefer to keep documentation as part
of the source tree, so that it is versioned along with the source tree and
so that only developers with check-in privileges can change it.  
Embedded documentation serves this latter purpose.  Both forms of documentation
use the exact same wiki markup language.  Some projects may choose to
use both forms of documentation at the same time.  Because the same
format is used, it is trivial to move a file from wiki to embedded documentation
or back again as the project evolves.

<h2>Bug-reports and check-in comments</h2>

The comments on check-ins and the text in the descriptions of bug reports
both use wiki formatting.  Exactly the same set of formatting rules apply.
There is never a need to learn one formatting language for documentation
and a different markup for bugs or for check-in comments.