Skip to content

Commit 9ba6640

Browse files
committed
Merge branch 'jm/api-strbuf-doc'
* jm/api-strbuf-doc: api-strbuf.txt minor typos
2 parents 7a3b4e3 + 97ea0d1 commit 9ba6640

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

Documentation/technical/api-strbuf.txt

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,10 @@ use the mem* functions than a str* one (memchr vs. strchr e.g.).
77
Though, one has to be careful about the fact that str* functions often
88
stop on NULs and that strbufs may have embedded NULs.
99

10-
An strbuf is NUL terminated for convenience, but no function in the
10+
A strbuf is NUL terminated for convenience, but no function in the
1111
strbuf API actually relies on the string being free of NULs.
1212

13-
strbufs has some invariants that are very important to keep in mind:
13+
strbufs have some invariants that are very important to keep in mind:
1414

1515
. The `buf` member is never NULL, so it can be used in any usual C
1616
string operations safely. strbuf's _have_ to be initialized either by
@@ -56,8 +56,8 @@ Data structures
5656
* `struct strbuf`
5757

5858
This is the string buffer structure. The `len` member can be used to
59-
determine the current length of the string, and `buf` member provides access to
60-
the string itself.
59+
determine the current length of the string, and `buf` member provides
60+
access to the string itself.
6161

6262
Functions
6363
---------
@@ -202,7 +202,7 @@ strbuf_addstr(sb, "immediate string");
202202

203203
`strbuf_addbuf`::
204204

205-
Copy the contents of an other buffer at the end of the current one.
205+
Copy the contents of another buffer at the end of the current one.
206206

207207
`strbuf_adddup`::
208208

0 commit comments

Comments
 (0)