path: root/Documentation/technical/protocol-capabilities.txt
diff options
authorRalf Wildenhues <>2010-01-31 13:24:39 (GMT)
committerJunio C Hamano <>2010-01-31 18:24:53 (GMT)
commit6a5d0b0a90789ed92cb87f1b69cfeef2a1db3566 (patch)
tree7e41d2a126b9090d7d3eaaa37c4dead8ce2a090a /Documentation/technical/protocol-capabilities.txt
parentb0883aa6c77111e88496bd0afe073caf68ab9f99 (diff)
Fix typos in technical documentation.
Signed-off-by: Ralf Wildenhues <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/technical/protocol-capabilities.txt')
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/technical/protocol-capabilities.txt b/Documentation/technical/protocol-capabilities.txt
index 1892d3e..fd1a593 100644
--- a/Documentation/technical/protocol-capabilities.txt
+++ b/Documentation/technical/protocol-capabilities.txt
@@ -60,7 +60,7 @@ doesn't, as in the following diagram:
If the client wants x,y and starts out by saying have F,S, the server
doesn't know what F,S is. Eventually the client says "have d" and
the server sends "ACK d continue" to let the client know to stop
-walking down that line (so don't send c-b-a), but its not done yet,
+walking down that line (so don't send c-b-a), but it's not done yet,
it needs a base for x. The client keeps going with S-R-Q, until a
gets reached, at which point the server has a clear base and it all
@@ -181,7 +181,7 @@ delete-refs
If the server sends back the 'delete-refs' capability, it means that
-it is capable of accepting an zero-id value as the target
+it is capable of accepting a zero-id value as the target
value of a reference update. It is not sent back by the client, it
simply informs the client that it can be sent zero-id values
to delete references.