Fossil SCM
Grammar tidyups for backoffice doc.
Commit
c500fa61cf648da8d660eefeff0051ceeb805c5cfc13b348b08cab1475cc0e33
Parent
59bb3743987706f…
1 file changed
+4
-4
+4
-4
| --- www/backoffice.md | ||
| +++ www/backoffice.md | ||
| @@ -35,11 +35,11 @@ | ||
| 35 | 35 | is started to do the work. |
| 36 | 36 | |
| 37 | 37 | This happens for every webpage, regardless of how that webpage is launched, |
| 38 | 38 | and regardless of the purpose of the webpage. This also happens on the |
| 39 | 39 | server for "[fossil sync](/help/sync)" and |
| 40 | -[fossil clone](/help/clone)" commands which are implemented as | |
| 40 | +"[fossil clone](/help/clone)" commands which are implemented as | |
| 41 | 41 | web requests - albeit requests that the human user never sees. |
| 42 | 42 | Web requests can arrive at the Fossil server via direct TCP/IP (for example |
| 43 | 43 | when Fossil is started using commands like "[fossil server](/help/server)") |
| 44 | 44 | or via [CGI](./server/any/cgi.md) or |
| 45 | 45 | [SCGI](./server/any/scgi.md) or via SSH. |
| @@ -93,17 +93,17 @@ | ||
| 93 | 93 | |
| 94 | 94 | Automatic Backoffice Does Not Work On Some Systems |
| 95 | 95 | -------------------------------------------------- |
| 96 | 96 | |
| 97 | 97 | We have observed that the automatic backoffice does not work on |
| 98 | -some system - OpenBSD in particular. We still do not understand why | |
| 98 | +some systems - OpenBSD in particular. We still do not understand why | |
| 99 | 99 | this is. (If you have insights, please share them on the |
| 100 | 100 | [Fossil Forum](https://fossil-scm.org/forum) so that we can perhaps |
| 101 | 101 | fix the problem.) For now, the backoffice must be run manually |
| 102 | 102 | on OpenBSD systems. |
| 103 | 103 | |
| 104 | -To set up fully-manual backoffice, first disable the automatic backoffice | |
| 104 | +To set up a fully-manual backoffice, first disable the automatic backoffice | |
| 105 | 105 | using the "[backoffice-disable](/help/backoffice-disable)" setting. |
| 106 | 106 | |
| 107 | 107 | fossil setting backoffice-disable on |
| 108 | 108 | |
| 109 | 109 | Then arrange to invoke the backoffice separately using a command |
| @@ -114,11 +114,11 @@ | ||
| 114 | 114 | Multiple repositories can be named. This one command will handle |
| 115 | 115 | launching the backoffice for all of them. There are additional useful |
| 116 | 116 | command-line options. See the "[fossil backoffice](/help/backoffice)" |
| 117 | 117 | documentation for details. |
| 118 | 118 | |
| 119 | -The backoffice processes run manually using the "fossil backoffice" | |
| 119 | +The backoffice processes that are run manually using the "fossil backoffice" | |
| 120 | 120 | command do not normally use a lease. That means that if you run the |
| 121 | 121 | "fossil backoffice" command with --poll and you forget to disable |
| 122 | 122 | automatic backoffice by setting the "backoffice-disable" flag, then |
| 123 | 123 | you might have one backoffice running due to a command and another due |
| 124 | 124 | to a webpage access, both at the same time. This is harmless. The |
| 125 | 125 |
| --- www/backoffice.md | |
| +++ www/backoffice.md | |
| @@ -35,11 +35,11 @@ | |
| 35 | is started to do the work. |
| 36 | |
| 37 | This happens for every webpage, regardless of how that webpage is launched, |
| 38 | and regardless of the purpose of the webpage. This also happens on the |
| 39 | server for "[fossil sync](/help/sync)" and |
| 40 | [fossil clone](/help/clone)" commands which are implemented as |
| 41 | web requests - albeit requests that the human user never sees. |
| 42 | Web requests can arrive at the Fossil server via direct TCP/IP (for example |
| 43 | when Fossil is started using commands like "[fossil server](/help/server)") |
| 44 | or via [CGI](./server/any/cgi.md) or |
| 45 | [SCGI](./server/any/scgi.md) or via SSH. |
| @@ -93,17 +93,17 @@ | |
| 93 | |
| 94 | Automatic Backoffice Does Not Work On Some Systems |
| 95 | -------------------------------------------------- |
| 96 | |
| 97 | We have observed that the automatic backoffice does not work on |
| 98 | some system - OpenBSD in particular. We still do not understand why |
| 99 | this is. (If you have insights, please share them on the |
| 100 | [Fossil Forum](https://fossil-scm.org/forum) so that we can perhaps |
| 101 | fix the problem.) For now, the backoffice must be run manually |
| 102 | on OpenBSD systems. |
| 103 | |
| 104 | To set up fully-manual backoffice, first disable the automatic backoffice |
| 105 | using the "[backoffice-disable](/help/backoffice-disable)" setting. |
| 106 | |
| 107 | fossil setting backoffice-disable on |
| 108 | |
| 109 | Then arrange to invoke the backoffice separately using a command |
| @@ -114,11 +114,11 @@ | |
| 114 | Multiple repositories can be named. This one command will handle |
| 115 | launching the backoffice for all of them. There are additional useful |
| 116 | command-line options. See the "[fossil backoffice](/help/backoffice)" |
| 117 | documentation for details. |
| 118 | |
| 119 | The backoffice processes run manually using the "fossil backoffice" |
| 120 | command do not normally use a lease. That means that if you run the |
| 121 | "fossil backoffice" command with --poll and you forget to disable |
| 122 | automatic backoffice by setting the "backoffice-disable" flag, then |
| 123 | you might have one backoffice running due to a command and another due |
| 124 | to a webpage access, both at the same time. This is harmless. The |
| 125 |
| --- www/backoffice.md | |
| +++ www/backoffice.md | |
| @@ -35,11 +35,11 @@ | |
| 35 | is started to do the work. |
| 36 | |
| 37 | This happens for every webpage, regardless of how that webpage is launched, |
| 38 | and regardless of the purpose of the webpage. This also happens on the |
| 39 | server for "[fossil sync](/help/sync)" and |
| 40 | "[fossil clone](/help/clone)" commands which are implemented as |
| 41 | web requests - albeit requests that the human user never sees. |
| 42 | Web requests can arrive at the Fossil server via direct TCP/IP (for example |
| 43 | when Fossil is started using commands like "[fossil server](/help/server)") |
| 44 | or via [CGI](./server/any/cgi.md) or |
| 45 | [SCGI](./server/any/scgi.md) or via SSH. |
| @@ -93,17 +93,17 @@ | |
| 93 | |
| 94 | Automatic Backoffice Does Not Work On Some Systems |
| 95 | -------------------------------------------------- |
| 96 | |
| 97 | We have observed that the automatic backoffice does not work on |
| 98 | some systems - OpenBSD in particular. We still do not understand why |
| 99 | this is. (If you have insights, please share them on the |
| 100 | [Fossil Forum](https://fossil-scm.org/forum) so that we can perhaps |
| 101 | fix the problem.) For now, the backoffice must be run manually |
| 102 | on OpenBSD systems. |
| 103 | |
| 104 | To set up a fully-manual backoffice, first disable the automatic backoffice |
| 105 | using the "[backoffice-disable](/help/backoffice-disable)" setting. |
| 106 | |
| 107 | fossil setting backoffice-disable on |
| 108 | |
| 109 | Then arrange to invoke the backoffice separately using a command |
| @@ -114,11 +114,11 @@ | |
| 114 | Multiple repositories can be named. This one command will handle |
| 115 | launching the backoffice for all of them. There are additional useful |
| 116 | command-line options. See the "[fossil backoffice](/help/backoffice)" |
| 117 | documentation for details. |
| 118 | |
| 119 | The backoffice processes that are run manually using the "fossil backoffice" |
| 120 | command do not normally use a lease. That means that if you run the |
| 121 | "fossil backoffice" command with --poll and you forget to disable |
| 122 | automatic backoffice by setting the "backoffice-disable" flag, then |
| 123 | you might have one backoffice running due to a command and another due |
| 124 | to a webpage access, both at the same time. This is harmless. The |
| 125 |