Fossil SCM
Grammar tweaks in point 2 of the "whyuseaserver.wiki" doc.
Commit
05e79793d85c082f3d188cd9b3aead7964226f7b9d2fe3684b4a17a8fc43fd30
Parent
a3a70a01aaee283…
1 file changed
+4
-3
+4
-3
| --- www/server/whyuseaserver.wiki | ||
| +++ www/server/whyuseaserver.wiki | ||
| @@ -27,13 +27,14 @@ | ||
| 27 | 27 | syncing their work.</b><p> |
| 28 | 28 | It is possible for developers to synchronize peer-to-peer but |
| 29 | 29 | that requires the developers coordinate the sync, which in turn |
| 30 | 30 | requires that the developers both want to sync at the same moment. |
| 31 | 31 | A server alleviates this time dependency by allowing each developer |
| 32 | - to sync whenever it is convenient (for example, automatically syncing | |
| 33 | - after each commit and before each update). Developers all stay | |
| 34 | - in sync with each other, without having to interrupt each other | |
| 32 | + to sync whenever it is convenient. For example, a developer may | |
| 33 | + choose to automatically sync | |
| 34 | + after each commit and before each update. Developers all stay | |
| 35 | + in sync with each other without having to interrupt each other | |
| 35 | 36 | constantly to set up a peer-to-peer sync. |
| 36 | 37 | |
| 37 | 38 | 3. <b>A server provides project leaders with up-to-date status.</b><p> |
| 38 | 39 | Project coordinators and BDFLs can click on a link or two at the |
| 39 | 40 | central Fossil server for a project, and quickly tell what is |
| 40 | 41 |
| --- www/server/whyuseaserver.wiki | |
| +++ www/server/whyuseaserver.wiki | |
| @@ -27,13 +27,14 @@ | |
| 27 | syncing their work.</b><p> |
| 28 | It is possible for developers to synchronize peer-to-peer but |
| 29 | that requires the developers coordinate the sync, which in turn |
| 30 | requires that the developers both want to sync at the same moment. |
| 31 | A server alleviates this time dependency by allowing each developer |
| 32 | to sync whenever it is convenient (for example, automatically syncing |
| 33 | after each commit and before each update). Developers all stay |
| 34 | in sync with each other, without having to interrupt each other |
| 35 | constantly to set up a peer-to-peer sync. |
| 36 | |
| 37 | 3. <b>A server provides project leaders with up-to-date status.</b><p> |
| 38 | Project coordinators and BDFLs can click on a link or two at the |
| 39 | central Fossil server for a project, and quickly tell what is |
| 40 |
| --- www/server/whyuseaserver.wiki | |
| +++ www/server/whyuseaserver.wiki | |
| @@ -27,13 +27,14 @@ | |
| 27 | syncing their work.</b><p> |
| 28 | It is possible for developers to synchronize peer-to-peer but |
| 29 | that requires the developers coordinate the sync, which in turn |
| 30 | requires that the developers both want to sync at the same moment. |
| 31 | A server alleviates this time dependency by allowing each developer |
| 32 | to sync whenever it is convenient. For example, a developer may |
| 33 | choose to automatically sync |
| 34 | after each commit and before each update. Developers all stay |
| 35 | in sync with each other without having to interrupt each other |
| 36 | constantly to set up a peer-to-peer sync. |
| 37 | |
| 38 | 3. <b>A server provides project leaders with up-to-date status.</b><p> |
| 39 | Project coordinators and BDFLs can click on a link or two at the |
| 40 | central Fossil server for a project, and quickly tell what is |
| 41 |