Fossil SCM
Fix typos in the sync documentation.
Commit
d3dabbb08c67750a6e2d2f58e360b986d215d49a
Parent
a2730fea395dd1a…
1 file changed
+3
-3
+3
-3
| --- www/sync.wiki | ||
| +++ www/sync.wiki | ||
| @@ -421,11 +421,11 @@ | ||
| 421 | 421 | unversioned files need to be synchronized. |
| 422 | 422 | The server might also send a uvigot card when it receives a uvgimme card |
| 423 | 423 | but its reply message size is already oversized and hence unable to hold |
| 424 | 424 | the usual uvfile reply. |
| 425 | 425 | |
| 426 | -<p>When a client receives a "uvigot" card, it checks to see if the the | |
| 426 | +<p>When a client receives a "uvigot" card, it checks to see if the | |
| 427 | 427 | file needs to be transfered from client to server or from server to client. |
| 428 | 428 | If a client-to-server transmission is needed, the client schedules that |
| 429 | 429 | transfer to occur on a subsequent HTTP request. If a server-to-client |
| 430 | 430 | transfer is needed, then the client sends a "uvgimme" card back to the |
| 431 | 431 | server to request the file content. |
| @@ -457,11 +457,11 @@ | ||
| 457 | 457 | </blockquote> |
| 458 | 458 | |
| 459 | 459 | <p>The <i>name</i> is the name of the unversioned file found on the |
| 460 | 460 | server that the client would like to have. When a server sees a |
| 461 | 461 | uvgimme card, it normally responses with a uvfile card, though it might |
| 462 | -also send anoter uvigot card if the HTTP reply is already oversized. | |
| 462 | +also send another uvigot card if the HTTP reply is already oversized. | |
| 463 | 463 | |
| 464 | 464 | <h3>3.8 Cookie Cards</h3> |
| 465 | 465 | |
| 466 | 466 | <p>A cookie card can be used by a server to record a small amount |
| 467 | 467 | of state information on a client. The server sends a cookie to the |
| @@ -859,11 +859,11 @@ | ||
| 859 | 859 | <ol> |
| 860 | 860 | <li>The client sends a "pragma uv-hash" card to the server. The argument |
| 861 | 861 | to the uv-hash pragma is a hash of all filesnames, mtimes, and |
| 862 | 862 | content hashes for the unversioned files held by the client. |
| 863 | 863 | <hr> |
| 864 | -<li>If the unversion content hash from the client matches the unversioned | |
| 864 | +<li>If the unversioned content hash from the client matches the unversioned | |
| 865 | 865 | content hash on the server, then nothing needs to be done and the |
| 866 | 866 | server no-ops. But if the hashes are different, then the server |
| 867 | 867 | replies with either a uv-pull-only or a uv-push-ok pragma followed by |
| 868 | 868 | uvigot cards for all unversioned files held on the server. |
| 869 | 869 | <hr> |
| 870 | 870 |
| --- www/sync.wiki | |
| +++ www/sync.wiki | |
| @@ -421,11 +421,11 @@ | |
| 421 | unversioned files need to be synchronized. |
| 422 | The server might also send a uvigot card when it receives a uvgimme card |
| 423 | but its reply message size is already oversized and hence unable to hold |
| 424 | the usual uvfile reply. |
| 425 | |
| 426 | <p>When a client receives a "uvigot" card, it checks to see if the the |
| 427 | file needs to be transfered from client to server or from server to client. |
| 428 | If a client-to-server transmission is needed, the client schedules that |
| 429 | transfer to occur on a subsequent HTTP request. If a server-to-client |
| 430 | transfer is needed, then the client sends a "uvgimme" card back to the |
| 431 | server to request the file content. |
| @@ -457,11 +457,11 @@ | |
| 457 | </blockquote> |
| 458 | |
| 459 | <p>The <i>name</i> is the name of the unversioned file found on the |
| 460 | server that the client would like to have. When a server sees a |
| 461 | uvgimme card, it normally responses with a uvfile card, though it might |
| 462 | also send anoter uvigot card if the HTTP reply is already oversized. |
| 463 | |
| 464 | <h3>3.8 Cookie Cards</h3> |
| 465 | |
| 466 | <p>A cookie card can be used by a server to record a small amount |
| 467 | of state information on a client. The server sends a cookie to the |
| @@ -859,11 +859,11 @@ | |
| 859 | <ol> |
| 860 | <li>The client sends a "pragma uv-hash" card to the server. The argument |
| 861 | to the uv-hash pragma is a hash of all filesnames, mtimes, and |
| 862 | content hashes for the unversioned files held by the client. |
| 863 | <hr> |
| 864 | <li>If the unversion content hash from the client matches the unversioned |
| 865 | content hash on the server, then nothing needs to be done and the |
| 866 | server no-ops. But if the hashes are different, then the server |
| 867 | replies with either a uv-pull-only or a uv-push-ok pragma followed by |
| 868 | uvigot cards for all unversioned files held on the server. |
| 869 | <hr> |
| 870 |
| --- www/sync.wiki | |
| +++ www/sync.wiki | |
| @@ -421,11 +421,11 @@ | |
| 421 | unversioned files need to be synchronized. |
| 422 | The server might also send a uvigot card when it receives a uvgimme card |
| 423 | but its reply message size is already oversized and hence unable to hold |
| 424 | the usual uvfile reply. |
| 425 | |
| 426 | <p>When a client receives a "uvigot" card, it checks to see if the |
| 427 | file needs to be transfered from client to server or from server to client. |
| 428 | If a client-to-server transmission is needed, the client schedules that |
| 429 | transfer to occur on a subsequent HTTP request. If a server-to-client |
| 430 | transfer is needed, then the client sends a "uvgimme" card back to the |
| 431 | server to request the file content. |
| @@ -457,11 +457,11 @@ | |
| 457 | </blockquote> |
| 458 | |
| 459 | <p>The <i>name</i> is the name of the unversioned file found on the |
| 460 | server that the client would like to have. When a server sees a |
| 461 | uvgimme card, it normally responses with a uvfile card, though it might |
| 462 | also send another uvigot card if the HTTP reply is already oversized. |
| 463 | |
| 464 | <h3>3.8 Cookie Cards</h3> |
| 465 | |
| 466 | <p>A cookie card can be used by a server to record a small amount |
| 467 | of state information on a client. The server sends a cookie to the |
| @@ -859,11 +859,11 @@ | |
| 859 | <ol> |
| 860 | <li>The client sends a "pragma uv-hash" card to the server. The argument |
| 861 | to the uv-hash pragma is a hash of all filesnames, mtimes, and |
| 862 | content hashes for the unversioned files held by the client. |
| 863 | <hr> |
| 864 | <li>If the unversioned content hash from the client matches the unversioned |
| 865 | content hash on the server, then nothing needs to be done and the |
| 866 | server no-ops. But if the hashes are different, then the server |
| 867 | replies with either a uv-pull-only or a uv-push-ok pragma followed by |
| 868 | uvigot cards for all unversioned files held on the server. |
| 869 | <hr> |
| 870 |