Fossil SCM
Grammar tweaks to previous
Commit
ccd5cacc51fce3781655d3dce8c19e774e70b3a64cc64fea85f398c2ecca4bb1
Parent
e583b48a0453c6a…
1 file changed
+3
-3
+3
-3
| --- www/glossary.md | ||
| +++ www/glossary.md | ||
| @@ -318,17 +318,17 @@ | ||
| 318 | 318 | the history. Then, having done so, links from that historical |
| 319 | 319 | version of the wiki document take you to the current versions of the |
| 320 | 320 | target documents, not to the version contemporaneous with the source |
| 321 | 321 | document. |
| 322 | 322 | |
| 323 | - The consequence is that if say something like… | |
| 323 | + The consequence is that if you say something like… | |
| 324 | 324 | |
| 325 | 325 | $ fossil up 2020-04-01 |
| 326 | 326 | $ fossil ui |
| 327 | 327 | |
| 328 | - …you will **not** see the wiki as of April Fool’s Day in 2020. | |
| 329 | - You’ll see the current wiki article versions, same as if you ran it | |
| 328 | + …you will **not** see the wiki as of April Fool’s Day in 2020, but | |
| 329 | + instead the current wiki article versions, the same as if you ran it | |
| 330 | 330 | from a check-out of the tip-of-trunk. |
| 331 | 331 | |
| 332 | 332 | Contrast embedded docs, which are not only version-controlled as |
| 333 | 333 | normal files are in Fossil, they participate in all the tagging, |
| 334 | 334 | branching, and other versioning features. There are several |
| 335 | 335 |
| --- www/glossary.md | |
| +++ www/glossary.md | |
| @@ -318,17 +318,17 @@ | |
| 318 | the history. Then, having done so, links from that historical |
| 319 | version of the wiki document take you to the current versions of the |
| 320 | target documents, not to the version contemporaneous with the source |
| 321 | document. |
| 322 | |
| 323 | The consequence is that if say something like… |
| 324 | |
| 325 | $ fossil up 2020-04-01 |
| 326 | $ fossil ui |
| 327 | |
| 328 | …you will **not** see the wiki as of April Fool’s Day in 2020. |
| 329 | You’ll see the current wiki article versions, same as if you ran it |
| 330 | from a check-out of the tip-of-trunk. |
| 331 | |
| 332 | Contrast embedded docs, which are not only version-controlled as |
| 333 | normal files are in Fossil, they participate in all the tagging, |
| 334 | branching, and other versioning features. There are several |
| 335 |
| --- www/glossary.md | |
| +++ www/glossary.md | |
| @@ -318,17 +318,17 @@ | |
| 318 | the history. Then, having done so, links from that historical |
| 319 | version of the wiki document take you to the current versions of the |
| 320 | target documents, not to the version contemporaneous with the source |
| 321 | document. |
| 322 | |
| 323 | The consequence is that if you say something like… |
| 324 | |
| 325 | $ fossil up 2020-04-01 |
| 326 | $ fossil ui |
| 327 | |
| 328 | …you will **not** see the wiki as of April Fool’s Day in 2020, but |
| 329 | instead the current wiki article versions, the same as if you ran it |
| 330 | from a check-out of the tip-of-trunk. |
| 331 | |
| 332 | Contrast embedded docs, which are not only version-controlled as |
| 333 | normal files are in Fossil, they participate in all the tagging, |
| 334 | branching, and other versioning features. There are several |
| 335 |