aboutsummaryrefslogtreecommitdiff
path: root/Documentation/technical
diff options
context:
space:
mode:
authorGuanqun Lu <guanqun.lu@gmail.com>2009-02-05 05:00:40 +0800
committerJunio C Hamano <gitster@pobox.com>2009-02-03 22:09:03 -0800
commitc9a8abcf9a9997d463a6a05668fd9a90a26df1f2 (patch)
tree0bc94267e6fa635f564a4b6af94388af1796f22c /Documentation/technical
parente1e4389832f32bb6ce029d6a6b110aa9ec768ea8 (diff)
downloadgit-c9a8abcf9a9997d463a6a05668fd9a90a26df1f2.tar.gz
git-c9a8abcf9a9997d463a6a05668fd9a90a26df1f2.tar.xz
fix typo in Documentation
Signed-off-by: Guanqun Lu <guanqun.lu@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/technical')
-rw-r--r--Documentation/technical/api-strbuf.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/technical/api-strbuf.txt b/Documentation/technical/api-strbuf.txt
index a9668e5f2..4242dc014 100644
--- a/Documentation/technical/api-strbuf.txt
+++ b/Documentation/technical/api-strbuf.txt
@@ -21,7 +21,7 @@ allocated memory or not), use `strbuf_detach()` to unwrap a memory
buffer from its strbuf shell in a safe way. That is the sole supported
way. This will give you a malloced buffer that you can later `free()`.
+
-However, it it totally safe to modify anything in the string pointed by
+However, it is totally safe to modify anything in the string pointed by
the `buf` member, between the indices `0` and `len-1` (inclusive).
. The `buf` member is a byte array that has at least `len + 1` bytes