Fossil SCM
Fixed a typo in documentation (closes ticket [1f82e0e1e])
Commit
6a5d3bb089576dcd7eca9415edebf5875a6af05a
Parent
ef80fd87f32b40b…
1 file changed
+1
-1
+1
-1
| --- www/wikitheory.wiki | ||
| +++ www/wikitheory.wiki | ||
| @@ -66,11 +66,11 @@ | ||
| 66 | 66 | of the source tree, so that it is versioned along with the source tree and |
| 67 | 67 | so that only developers with check-in privileges can change it. |
| 68 | 68 | Embedded documentation serves this latter purpose. Both forms of documentation |
| 69 | 69 | use the exact same wiki markup language. Some projects may choose to |
| 70 | 70 | use both forms of documentation at the same time. Because the same |
| 71 | -format is used, it is trivial to move file from wiki to embedded documentation | |
| 71 | +format is used, it is trivial to move a file from wiki to embedded documentation | |
| 72 | 72 | or back again as the project evolves. |
| 73 | 73 | |
| 74 | 74 | <h2>Bug-reports and check-in comments</h2> |
| 75 | 75 | |
| 76 | 76 | The comments on check-ins and the text in the descriptions of bug reports |
| 77 | 77 |
| --- www/wikitheory.wiki | |
| +++ www/wikitheory.wiki | |
| @@ -66,11 +66,11 @@ | |
| 66 | of the source tree, so that it is versioned along with the source tree and |
| 67 | so that only developers with check-in privileges can change it. |
| 68 | Embedded documentation serves this latter purpose. Both forms of documentation |
| 69 | use the exact same wiki markup language. Some projects may choose to |
| 70 | use both forms of documentation at the same time. Because the same |
| 71 | format is used, it is trivial to move file from wiki to embedded documentation |
| 72 | or back again as the project evolves. |
| 73 | |
| 74 | <h2>Bug-reports and check-in comments</h2> |
| 75 | |
| 76 | The comments on check-ins and the text in the descriptions of bug reports |
| 77 |
| --- www/wikitheory.wiki | |
| +++ www/wikitheory.wiki | |
| @@ -66,11 +66,11 @@ | |
| 66 | of the source tree, so that it is versioned along with the source tree and |
| 67 | so that only developers with check-in privileges can change it. |
| 68 | Embedded documentation serves this latter purpose. Both forms of documentation |
| 69 | use the exact same wiki markup language. Some projects may choose to |
| 70 | use both forms of documentation at the same time. Because the same |
| 71 | format is used, it is trivial to move a file from wiki to embedded documentation |
| 72 | or back again as the project evolves. |
| 73 | |
| 74 | <h2>Bug-reports and check-in comments</h2> |
| 75 | |
| 76 | The comments on check-ins and the text in the descriptions of bug reports |
| 77 |