Fossil SCM
Fix various documentation typos.
Commit
3fec387cc3a0fff810321673f6e1f5a06718e36af95bba1ea8ba38c31a4e01d2
Parent
cd80b9f70ff0081…
5 files changed
+1
+2
-2
+2
-2
+4
-3
+3
-2
+1
| --- www/changes.wiki | ||
| +++ www/changes.wiki | ||
| @@ -32,10 +32,11 @@ | ||
| 32 | 32 | list of the "[/help?cmd=all|fossil all ui]" command. |
| 33 | 33 | * Administrators can configure [./alerts.md|email alerts] to expire |
| 34 | 34 | a specific number of days (ex: 365) after the last user contact with |
| 35 | 35 | the Fossil server. This prevents alert emails being sent to |
| 36 | 36 | abandoned email accounts forever. |
| 37 | + * Update the built-in SQLite to version 3.36.0. | |
| 37 | 38 | |
| 38 | 39 | <a name='v2_15'></a> |
| 39 | 40 | <h2>Changes for Version 2.15 (2021-03-26) and Patch 2.15.1 on (2021-04-07) |
| 40 | 41 | and 2.15.2 on (2021-06-15)</h2> |
| 41 | 42 | * <b>Patch 2.15.2:</b> Fix the client-side TLS so that it verifies that the |
| 42 | 43 |
| --- www/changes.wiki | |
| +++ www/changes.wiki | |
| @@ -32,10 +32,11 @@ | |
| 32 | list of the "[/help?cmd=all|fossil all ui]" command. |
| 33 | * Administrators can configure [./alerts.md|email alerts] to expire |
| 34 | a specific number of days (ex: 365) after the last user contact with |
| 35 | the Fossil server. This prevents alert emails being sent to |
| 36 | abandoned email accounts forever. |
| 37 | |
| 38 | <a name='v2_15'></a> |
| 39 | <h2>Changes for Version 2.15 (2021-03-26) and Patch 2.15.1 on (2021-04-07) |
| 40 | and 2.15.2 on (2021-06-15)</h2> |
| 41 | * <b>Patch 2.15.2:</b> Fix the client-side TLS so that it verifies that the |
| 42 |
| --- www/changes.wiki | |
| +++ www/changes.wiki | |
| @@ -32,10 +32,11 @@ | |
| 32 | list of the "[/help?cmd=all|fossil all ui]" command. |
| 33 | * Administrators can configure [./alerts.md|email alerts] to expire |
| 34 | a specific number of days (ex: 365) after the last user contact with |
| 35 | the Fossil server. This prevents alert emails being sent to |
| 36 | abandoned email accounts forever. |
| 37 | * Update the built-in SQLite to version 3.36.0. |
| 38 | |
| 39 | <a name='v2_15'></a> |
| 40 | <h2>Changes for Version 2.15 (2021-03-26) and Patch 2.15.1 on (2021-04-07) |
| 41 | and 2.15.2 on (2021-06-15)</h2> |
| 42 | * <b>Patch 2.15.2:</b> Fix the client-side TLS so that it verifies that the |
| 43 |
+2
-2
| --- www/customskin.md | ||
| +++ www/customskin.md | ||
| @@ -238,11 +238,11 @@ | ||
| 238 | 238 | part of the overall web page.</dd> |
| 239 | 239 | |
| 240 | 240 | <dt><b>js.txt</b></dt><dd> |
| 241 | 241 | |
| 242 | 242 | <p>The js.txt file is optional. It is intended to be javascript. |
| 243 | -The complete text of this javascript is might be inserted into | |
| 243 | +The complete text of this javascript might be inserted into | |
| 244 | 244 | the Content Footer, after being processed using TH1, using |
| 245 | 245 | code like the following in the "footer.txt" file: |
| 246 | 246 | |
| 247 | 247 | <blockquote><pre> |
| 248 | 248 | <script nonce="$nonce"> |
| @@ -354,11 +354,11 @@ | ||
| 354 | 354 | |
| 355 | 355 | The menu bar of the default skin has an entry to open a drop-down menu with |
| 356 | 356 | additional navigation links, represented by the ≡ button (hence the name |
| 357 | 357 | "hamburger menu"). The Javascript logic to open and close the hamburger menu |
| 358 | 358 | when the button is clicked is usually handled by a script named |
| 359 | -"hbmenu.js" that is one of the [built-in resource files](/test-builtin-list) | |
| 359 | +"hbmenu.js" that is one of the [built-in resource files](/test-builtin-files) | |
| 360 | 360 | that are part of Fossil. |
| 361 | 361 | |
| 362 | 362 | The ≡ button for the hamburger menu is added to the menu bar by the following |
| 363 | 363 | TH1 commands in the `header.txt` file, right before the menu bar links: |
| 364 | 364 | |
| 365 | 365 |
| --- www/customskin.md | |
| +++ www/customskin.md | |
| @@ -238,11 +238,11 @@ | |
| 238 | part of the overall web page.</dd> |
| 239 | |
| 240 | <dt><b>js.txt</b></dt><dd> |
| 241 | |
| 242 | <p>The js.txt file is optional. It is intended to be javascript. |
| 243 | The complete text of this javascript is might be inserted into |
| 244 | the Content Footer, after being processed using TH1, using |
| 245 | code like the following in the "footer.txt" file: |
| 246 | |
| 247 | <blockquote><pre> |
| 248 | <script nonce="$nonce"> |
| @@ -354,11 +354,11 @@ | |
| 354 | |
| 355 | The menu bar of the default skin has an entry to open a drop-down menu with |
| 356 | additional navigation links, represented by the ≡ button (hence the name |
| 357 | "hamburger menu"). The Javascript logic to open and close the hamburger menu |
| 358 | when the button is clicked is usually handled by a script named |
| 359 | "hbmenu.js" that is one of the [built-in resource files](/test-builtin-list) |
| 360 | that are part of Fossil. |
| 361 | |
| 362 | The ≡ button for the hamburger menu is added to the menu bar by the following |
| 363 | TH1 commands in the `header.txt` file, right before the menu bar links: |
| 364 | |
| 365 |
| --- www/customskin.md | |
| +++ www/customskin.md | |
| @@ -238,11 +238,11 @@ | |
| 238 | part of the overall web page.</dd> |
| 239 | |
| 240 | <dt><b>js.txt</b></dt><dd> |
| 241 | |
| 242 | <p>The js.txt file is optional. It is intended to be javascript. |
| 243 | The complete text of this javascript might be inserted into |
| 244 | the Content Footer, after being processed using TH1, using |
| 245 | code like the following in the "footer.txt" file: |
| 246 | |
| 247 | <blockquote><pre> |
| 248 | <script nonce="$nonce"> |
| @@ -354,11 +354,11 @@ | |
| 354 | |
| 355 | The menu bar of the default skin has an entry to open a drop-down menu with |
| 356 | additional navigation links, represented by the ≡ button (hence the name |
| 357 | "hamburger menu"). The Javascript logic to open and close the hamburger menu |
| 358 | when the button is clicked is usually handled by a script named |
| 359 | "hbmenu.js" that is one of the [built-in resource files](/test-builtin-files) |
| 360 | that are part of Fossil. |
| 361 | |
| 362 | The ≡ button for the hamburger menu is added to the menu bar by the following |
| 363 | TH1 commands in the `header.txt` file, right before the menu bar links: |
| 364 | |
| 365 |
+2
-2
| --- www/defcsp.md | ||
| +++ www/defcsp.md | ||
| @@ -1,19 +1,19 @@ | ||
| 1 | 1 | # The Default Content Security Policy (CSP) |
| 2 | 2 | |
| 3 | 3 | When Fossil’s web interface generates an HTML page, it normally includes |
| 4 | 4 | a [Content Security Policy][csp] (CSP) in the `<head>`. The CSP specifies |
| 5 | 5 | allowed sources for external resources such as images, |
| 6 | -CSS, javascript, and so froth. | |
| 6 | +CSS, javascript, and so forth. | |
| 7 | 7 | The purpose of CSP is to provide an extra layer of protection against |
| 8 | 8 | [cross-site scripting][xss] (XSS) and code injection |
| 9 | 9 | attacks. Compatible web browsers will not use external resources unless |
| 10 | 10 | they are specifically allowed by the CSP, which dramatically reduces |
| 11 | 11 | the attack surface of the application. |
| 12 | 12 | |
| 13 | 13 | Fossil does not rely on CSP for security. |
| 14 | -A Fossil server should be secure from attack even with out CSP. | |
| 14 | +A Fossil server should be secure from attack even without CSP. | |
| 15 | 15 | Fossil includes built-in server-side content filtering logic. |
| 16 | 16 | For example, Fossil purposely breaks `<script>` tags when it finds |
| 17 | 17 | them in Markdown and Fossil Wiki documents. And the Fossil build |
| 18 | 18 | process scans the source code for potential injection vulnerabilities |
| 19 | 19 | and refuses to compile if any problems are found. |
| 20 | 20 |
| --- www/defcsp.md | |
| +++ www/defcsp.md | |
| @@ -1,19 +1,19 @@ | |
| 1 | # The Default Content Security Policy (CSP) |
| 2 | |
| 3 | When Fossil’s web interface generates an HTML page, it normally includes |
| 4 | a [Content Security Policy][csp] (CSP) in the `<head>`. The CSP specifies |
| 5 | allowed sources for external resources such as images, |
| 6 | CSS, javascript, and so froth. |
| 7 | The purpose of CSP is to provide an extra layer of protection against |
| 8 | [cross-site scripting][xss] (XSS) and code injection |
| 9 | attacks. Compatible web browsers will not use external resources unless |
| 10 | they are specifically allowed by the CSP, which dramatically reduces |
| 11 | the attack surface of the application. |
| 12 | |
| 13 | Fossil does not rely on CSP for security. |
| 14 | A Fossil server should be secure from attack even with out CSP. |
| 15 | Fossil includes built-in server-side content filtering logic. |
| 16 | For example, Fossil purposely breaks `<script>` tags when it finds |
| 17 | them in Markdown and Fossil Wiki documents. And the Fossil build |
| 18 | process scans the source code for potential injection vulnerabilities |
| 19 | and refuses to compile if any problems are found. |
| 20 |
| --- www/defcsp.md | |
| +++ www/defcsp.md | |
| @@ -1,19 +1,19 @@ | |
| 1 | # The Default Content Security Policy (CSP) |
| 2 | |
| 3 | When Fossil’s web interface generates an HTML page, it normally includes |
| 4 | a [Content Security Policy][csp] (CSP) in the `<head>`. The CSP specifies |
| 5 | allowed sources for external resources such as images, |
| 6 | CSS, javascript, and so forth. |
| 7 | The purpose of CSP is to provide an extra layer of protection against |
| 8 | [cross-site scripting][xss] (XSS) and code injection |
| 9 | attacks. Compatible web browsers will not use external resources unless |
| 10 | they are specifically allowed by the CSP, which dramatically reduces |
| 11 | the attack surface of the application. |
| 12 | |
| 13 | Fossil does not rely on CSP for security. |
| 14 | A Fossil server should be secure from attack even without CSP. |
| 15 | Fossil includes built-in server-side content filtering logic. |
| 16 | For example, Fossil purposely breaks `<script>` tags when it finds |
| 17 | them in Markdown and Fossil Wiki documents. And the Fossil build |
| 18 | process scans the source code for potential injection vulnerabilities |
| 19 | and refuses to compile if any problems are found. |
| 20 |
+4
-3
| --- www/index.wiki | ||
| +++ www/index.wiki | ||
| @@ -24,11 +24,12 @@ | ||
| 24 | 24 | |
| 25 | 25 | 1. <b>Project Management</b> - |
| 26 | 26 | In addition to doing [./concepts.wiki | distributed version control] |
| 27 | 27 | like Git and Mercurial, |
| 28 | 28 | Fossil also supports [./bugtheory.wiki | bug tracking], |
| 29 | - [./wikitheory.wiki | wiki], [./forum.wiki | forum], [./chat.md | chat], and | |
| 29 | + [./wikitheory.wiki | wiki], [./forum.wiki | forum], | |
| 30 | + [./alerts.md|email alerts], [./chat.md | chat], and | |
| 30 | 31 | [./event.wiki | technotes]. |
| 31 | 32 | |
| 32 | 33 | 2. <b>Built-in Web Interface</b> - |
| 33 | 34 | Fossil has a built-in, [/skins | themeable], [./serverext.wiki | extensible], |
| 34 | 35 | and intuitive [./webui.wiki | web interface] |
| @@ -95,12 +96,12 @@ | ||
| 95 | 96 | <hr> |
| 96 | 97 | <h3>Quick Start</h3> |
| 97 | 98 | |
| 98 | 99 | 1. [/uv/download.html|Download] or install using a package manager or |
| 99 | 100 | [./build.wiki|compile from sources]. |
| 100 | - 2. <tt>fossil init</tt> <i>REPOSTORE-DIR/new-repository</i> | |
| 101 | - 3. <tt>fossil open</tt> <i>REPOSTORE-DIR/new-repository</i> | |
| 101 | + 2. <tt>fossil init</tt> <i>REPOSITORY-DIR/new-repository</i> | |
| 102 | + 3. <tt>fossil open</tt> <i>REPOSITORY-DIR/new-repository</i> | |
| 102 | 103 | 4. <tt>fossil add</tt> <i>files-or-directories</i> |
| 103 | 104 | 5. <tt>fossil commit -m</tt> "<i>commit message</i>" |
| 104 | 105 | 6. <tt>fossil ui</tt> |
| 105 | 106 | 7. Repeat steps 4, 5, and 6, in any order, as necessary. |
| 106 | 107 | See the [./quickstart.wiki|Quick Start Guide] for more detail. |
| 107 | 108 |
| --- www/index.wiki | |
| +++ www/index.wiki | |
| @@ -24,11 +24,12 @@ | |
| 24 | |
| 25 | 1. <b>Project Management</b> - |
| 26 | In addition to doing [./concepts.wiki | distributed version control] |
| 27 | like Git and Mercurial, |
| 28 | Fossil also supports [./bugtheory.wiki | bug tracking], |
| 29 | [./wikitheory.wiki | wiki], [./forum.wiki | forum], [./chat.md | chat], and |
| 30 | [./event.wiki | technotes]. |
| 31 | |
| 32 | 2. <b>Built-in Web Interface</b> - |
| 33 | Fossil has a built-in, [/skins | themeable], [./serverext.wiki | extensible], |
| 34 | and intuitive [./webui.wiki | web interface] |
| @@ -95,12 +96,12 @@ | |
| 95 | <hr> |
| 96 | <h3>Quick Start</h3> |
| 97 | |
| 98 | 1. [/uv/download.html|Download] or install using a package manager or |
| 99 | [./build.wiki|compile from sources]. |
| 100 | 2. <tt>fossil init</tt> <i>REPOSTORE-DIR/new-repository</i> |
| 101 | 3. <tt>fossil open</tt> <i>REPOSTORE-DIR/new-repository</i> |
| 102 | 4. <tt>fossil add</tt> <i>files-or-directories</i> |
| 103 | 5. <tt>fossil commit -m</tt> "<i>commit message</i>" |
| 104 | 6. <tt>fossil ui</tt> |
| 105 | 7. Repeat steps 4, 5, and 6, in any order, as necessary. |
| 106 | See the [./quickstart.wiki|Quick Start Guide] for more detail. |
| 107 |
| --- www/index.wiki | |
| +++ www/index.wiki | |
| @@ -24,11 +24,12 @@ | |
| 24 | |
| 25 | 1. <b>Project Management</b> - |
| 26 | In addition to doing [./concepts.wiki | distributed version control] |
| 27 | like Git and Mercurial, |
| 28 | Fossil also supports [./bugtheory.wiki | bug tracking], |
| 29 | [./wikitheory.wiki | wiki], [./forum.wiki | forum], |
| 30 | [./alerts.md|email alerts], [./chat.md | chat], and |
| 31 | [./event.wiki | technotes]. |
| 32 | |
| 33 | 2. <b>Built-in Web Interface</b> - |
| 34 | Fossil has a built-in, [/skins | themeable], [./serverext.wiki | extensible], |
| 35 | and intuitive [./webui.wiki | web interface] |
| @@ -95,12 +96,12 @@ | |
| 96 | <hr> |
| 97 | <h3>Quick Start</h3> |
| 98 | |
| 99 | 1. [/uv/download.html|Download] or install using a package manager or |
| 100 | [./build.wiki|compile from sources]. |
| 101 | 2. <tt>fossil init</tt> <i>REPOSITORY-DIR/new-repository</i> |
| 102 | 3. <tt>fossil open</tt> <i>REPOSITORY-DIR/new-repository</i> |
| 103 | 4. <tt>fossil add</tt> <i>files-or-directories</i> |
| 104 | 5. <tt>fossil commit -m</tt> "<i>commit message</i>" |
| 105 | 6. <tt>fossil ui</tt> |
| 106 | 7. Repeat steps 4, 5, and 6, in any order, as necessary. |
| 107 | See the [./quickstart.wiki|Quick Start Guide] for more detail. |
| 108 |
+3
-2
| --- www/th1.md | ||
| +++ www/th1.md | ||
| @@ -110,11 +110,11 @@ | ||
| 110 | 110 | |
| 111 | 111 | |
| 112 | 112 | Summary of Core TH1 Commands |
| 113 | 113 | ---------------------------- |
| 114 | 114 | |
| 115 | -The original Tcl language after when TH1 is modeled has a very rich | |
| 115 | +The original Tcl language (after which TH1 is modeled) has a very rich | |
| 116 | 116 | repertoire of commands. TH1, as it is designed to be minimalist and |
| 117 | 117 | embedded has a greatly reduced command set. The following bullets |
| 118 | 118 | summarize the commands available in TH1: |
| 119 | 119 | |
| 120 | 120 | * array exists VARNAME |
| @@ -284,11 +284,12 @@ | ||
| 284 | 284 | Added in Fossil 2.15. |
| 285 | 285 | |
| 286 | 286 | * capexpr CAPABILITY-EXPR |
| 287 | 287 | |
| 288 | 288 | The capability expression is a list. Each term of the list is a |
| 289 | -cluster of capability letters. The overall expression is true if any | |
| 289 | +cluster of [capability letters](./caps/ref.html). | |
| 290 | +The overall expression is true if any | |
| 290 | 291 | one term is true. A single term is true if all letters within that |
| 291 | 292 | term are true. Or, if the term begins with "!", then the term is true |
| 292 | 293 | if none of the terms or true. Or, if the term begins with "@" then |
| 293 | 294 | the term is true if all of the capability letters in that term are |
| 294 | 295 | available to the "anonymous" user. Or, if the term is "*" then it is |
| 295 | 296 |
| --- www/th1.md | |
| +++ www/th1.md | |
| @@ -110,11 +110,11 @@ | |
| 110 | |
| 111 | |
| 112 | Summary of Core TH1 Commands |
| 113 | ---------------------------- |
| 114 | |
| 115 | The original Tcl language after when TH1 is modeled has a very rich |
| 116 | repertoire of commands. TH1, as it is designed to be minimalist and |
| 117 | embedded has a greatly reduced command set. The following bullets |
| 118 | summarize the commands available in TH1: |
| 119 | |
| 120 | * array exists VARNAME |
| @@ -284,11 +284,12 @@ | |
| 284 | Added in Fossil 2.15. |
| 285 | |
| 286 | * capexpr CAPABILITY-EXPR |
| 287 | |
| 288 | The capability expression is a list. Each term of the list is a |
| 289 | cluster of capability letters. The overall expression is true if any |
| 290 | one term is true. A single term is true if all letters within that |
| 291 | term are true. Or, if the term begins with "!", then the term is true |
| 292 | if none of the terms or true. Or, if the term begins with "@" then |
| 293 | the term is true if all of the capability letters in that term are |
| 294 | available to the "anonymous" user. Or, if the term is "*" then it is |
| 295 |
| --- www/th1.md | |
| +++ www/th1.md | |
| @@ -110,11 +110,11 @@ | |
| 110 | |
| 111 | |
| 112 | Summary of Core TH1 Commands |
| 113 | ---------------------------- |
| 114 | |
| 115 | The original Tcl language (after which TH1 is modeled) has a very rich |
| 116 | repertoire of commands. TH1, as it is designed to be minimalist and |
| 117 | embedded has a greatly reduced command set. The following bullets |
| 118 | summarize the commands available in TH1: |
| 119 | |
| 120 | * array exists VARNAME |
| @@ -284,11 +284,12 @@ | |
| 284 | Added in Fossil 2.15. |
| 285 | |
| 286 | * capexpr CAPABILITY-EXPR |
| 287 | |
| 288 | The capability expression is a list. Each term of the list is a |
| 289 | cluster of [capability letters](./caps/ref.html). |
| 290 | The overall expression is true if any |
| 291 | one term is true. A single term is true if all letters within that |
| 292 | term are true. Or, if the term begins with "!", then the term is true |
| 293 | if none of the terms or true. Or, if the term begins with "@" then |
| 294 | the term is true if all of the capability letters in that term are |
| 295 | available to the "anonymous" user. Or, if the term is "*" then it is |
| 296 |