Fossil SCM
Fix minor typos in documentation.
Commit
a9819ba2671226a88379405025dd419ed39a7afa
Parent
8b4aaef2f515b0e…
1 file changed
+6
-6
+6
-6
| --- www/sync.wiki | ||
| +++ www/sync.wiki | ||
| @@ -124,11 +124,11 @@ | ||
| 124 | 124 | section details the "x-fossil" content type.</p> |
| 125 | 125 | |
| 126 | 126 | <h3>3.1 Line-oriented Format</h3> |
| 127 | 127 | |
| 128 | 128 | <p>The x-fossil content type consists of zero or more "cards". Cards |
| 129 | -are separate by the newline character ("\n"). Leading and trailing | |
| 129 | +are separated by the newline character ("\n"). Leading and trailing | |
| 130 | 130 | whitespace on a card is ignored. Blank cards are ignored.</p> |
| 131 | 131 | |
| 132 | 132 | <p>Each card is divided into zero or more space separated tokens. |
| 133 | 133 | The first token on each card is the operator. Subsequent tokens |
| 134 | 134 | are arguments. The set of operators understood by servers is slightly |
| @@ -196,13 +196,13 @@ | ||
| 196 | 196 | the delta, so both client and server should remember deltas |
| 197 | 197 | and be able to apply them when their source arrives.</p> |
| 198 | 198 | |
| 199 | 199 | <h3>3.4 Push and Pull Cards</h3> |
| 200 | 200 | |
| 201 | -<p>Among of the first cards in a client-to-server message are | |
| 202 | -the push and pull cards. The push card tell the server that | |
| 203 | -the client is pushing content. The pull card tell the server | |
| 201 | +<p>Among the first cards in a client-to-server message are | |
| 202 | +the push and pull cards. The push card tells the server that | |
| 203 | +the client is pushing content. The pull card tells the server | |
| 204 | 204 | that the client wants to pull content. In the event of a sync, |
| 205 | 205 | both cards are sent. The format is as follows:</p> |
| 206 | 206 | |
| 207 | 207 | <blockquote> |
| 208 | 208 | <b>push</b> <i>servercode projectcode</i><br> |
| @@ -238,21 +238,21 @@ | ||
| 238 | 238 | |
| 239 | 239 | <p>The latest clients send a two-argument clone message with a |
| 240 | 240 | protocol version of "2". (Future versions of Fossil might use larger |
| 241 | 241 | protocol version numbers.) The sequence-number sent is the number |
| 242 | 242 | of artifacts received so far. For the first clone message, the |
| 243 | -sequence number if 0. The server will respond by sending file | |
| 243 | +sequence number is 0. The server will respond by sending file | |
| 244 | 244 | cards for some number of artifacts up to the maximum message size. |
| 245 | 245 | |
| 246 | 246 | <p>The server will also send a single "clone_seqno" card to the client |
| 247 | 247 | so that the client can know where the server left off. |
| 248 | 248 | |
| 249 | 249 | <blockquote> |
| 250 | 250 | <b>clone_seqno</b> <i>sequence-number</i> |
| 251 | 251 | </blockquote> |
| 252 | 252 | |
| 253 | -<p>The clone message in subquence HTTP requests for the same clone | |
| 253 | +<p>The clone message in subsequent HTTP requests for the same clone | |
| 254 | 254 | operation will use the sequence-number from the |
| 255 | 255 | clone_seqno of the previous reply.</p> |
| 256 | 256 | |
| 257 | 257 | <p>In response to an initial clone message, the server also sends the client |
| 258 | 258 | a push message so that the client can discover the projectcode for |
| 259 | 259 |
| --- www/sync.wiki | |
| +++ www/sync.wiki | |
| @@ -124,11 +124,11 @@ | |
| 124 | section details the "x-fossil" content type.</p> |
| 125 | |
| 126 | <h3>3.1 Line-oriented Format</h3> |
| 127 | |
| 128 | <p>The x-fossil content type consists of zero or more "cards". Cards |
| 129 | are separate by the newline character ("\n"). Leading and trailing |
| 130 | whitespace on a card is ignored. Blank cards are ignored.</p> |
| 131 | |
| 132 | <p>Each card is divided into zero or more space separated tokens. |
| 133 | The first token on each card is the operator. Subsequent tokens |
| 134 | are arguments. The set of operators understood by servers is slightly |
| @@ -196,13 +196,13 @@ | |
| 196 | the delta, so both client and server should remember deltas |
| 197 | and be able to apply them when their source arrives.</p> |
| 198 | |
| 199 | <h3>3.4 Push and Pull Cards</h3> |
| 200 | |
| 201 | <p>Among of the first cards in a client-to-server message are |
| 202 | the push and pull cards. The push card tell the server that |
| 203 | the client is pushing content. The pull card tell the server |
| 204 | that the client wants to pull content. In the event of a sync, |
| 205 | both cards are sent. The format is as follows:</p> |
| 206 | |
| 207 | <blockquote> |
| 208 | <b>push</b> <i>servercode projectcode</i><br> |
| @@ -238,21 +238,21 @@ | |
| 238 | |
| 239 | <p>The latest clients send a two-argument clone message with a |
| 240 | protocol version of "2". (Future versions of Fossil might use larger |
| 241 | protocol version numbers.) The sequence-number sent is the number |
| 242 | of artifacts received so far. For the first clone message, the |
| 243 | sequence number if 0. The server will respond by sending file |
| 244 | cards for some number of artifacts up to the maximum message size. |
| 245 | |
| 246 | <p>The server will also send a single "clone_seqno" card to the client |
| 247 | so that the client can know where the server left off. |
| 248 | |
| 249 | <blockquote> |
| 250 | <b>clone_seqno</b> <i>sequence-number</i> |
| 251 | </blockquote> |
| 252 | |
| 253 | <p>The clone message in subquence HTTP requests for the same clone |
| 254 | operation will use the sequence-number from the |
| 255 | clone_seqno of the previous reply.</p> |
| 256 | |
| 257 | <p>In response to an initial clone message, the server also sends the client |
| 258 | a push message so that the client can discover the projectcode for |
| 259 |
| --- www/sync.wiki | |
| +++ www/sync.wiki | |
| @@ -124,11 +124,11 @@ | |
| 124 | section details the "x-fossil" content type.</p> |
| 125 | |
| 126 | <h3>3.1 Line-oriented Format</h3> |
| 127 | |
| 128 | <p>The x-fossil content type consists of zero or more "cards". Cards |
| 129 | are separated by the newline character ("\n"). Leading and trailing |
| 130 | whitespace on a card is ignored. Blank cards are ignored.</p> |
| 131 | |
| 132 | <p>Each card is divided into zero or more space separated tokens. |
| 133 | The first token on each card is the operator. Subsequent tokens |
| 134 | are arguments. The set of operators understood by servers is slightly |
| @@ -196,13 +196,13 @@ | |
| 196 | the delta, so both client and server should remember deltas |
| 197 | and be able to apply them when their source arrives.</p> |
| 198 | |
| 199 | <h3>3.4 Push and Pull Cards</h3> |
| 200 | |
| 201 | <p>Among the first cards in a client-to-server message are |
| 202 | the push and pull cards. The push card tells the server that |
| 203 | the client is pushing content. The pull card tells the server |
| 204 | that the client wants to pull content. In the event of a sync, |
| 205 | both cards are sent. The format is as follows:</p> |
| 206 | |
| 207 | <blockquote> |
| 208 | <b>push</b> <i>servercode projectcode</i><br> |
| @@ -238,21 +238,21 @@ | |
| 238 | |
| 239 | <p>The latest clients send a two-argument clone message with a |
| 240 | protocol version of "2". (Future versions of Fossil might use larger |
| 241 | protocol version numbers.) The sequence-number sent is the number |
| 242 | of artifacts received so far. For the first clone message, the |
| 243 | sequence number is 0. The server will respond by sending file |
| 244 | cards for some number of artifacts up to the maximum message size. |
| 245 | |
| 246 | <p>The server will also send a single "clone_seqno" card to the client |
| 247 | so that the client can know where the server left off. |
| 248 | |
| 249 | <blockquote> |
| 250 | <b>clone_seqno</b> <i>sequence-number</i> |
| 251 | </blockquote> |
| 252 | |
| 253 | <p>The clone message in subsequent HTTP requests for the same clone |
| 254 | operation will use the sequence-number from the |
| 255 | clone_seqno of the previous reply.</p> |
| 256 | |
| 257 | <p>In response to an initial clone message, the server also sends the client |
| 258 | a push message so that the client can discover the projectcode for |
| 259 |