summaryrefslogtreecommitdiffstats
path: root/Etc
diff options
context:
space:
mode:
authorDoug Kearns <[email protected]>2009-01-22 12:12:13 +0000
committerDoug Kearns <[email protected]>2009-01-22 12:12:13 +0000
commita5260beedb4a8fe7ac3c2909a443039982740025 (patch)
treeda042d4c61fc1d07862391aec5457f15ea45916f /Etc
parent52bb631ccbe563793c5cd1ca837c789c3f8bb27b (diff)
downloadzsh-a5260beedb4a8fe7ac3c2909a443039982740025.tar.gz
zsh-a5260beedb4a8fe7ac3c2909a443039982740025.tar.bz2
zsh-a5260beedb4a8fe7ac3c2909a443039982740025.zip
unposted: Fix some typos in the development guide
Diffstat (limited to 'Etc')
-rw-r--r--Etc/zsh-development-guide6
1 files changed, 3 insertions, 3 deletions
diff --git a/Etc/zsh-development-guide b/Etc/zsh-development-guide
index 4c3f5225..b19f4825 100644
--- a/Etc/zsh-development-guide
+++ b/Etc/zsh-development-guide
@@ -300,7 +300,7 @@ is generic information.
`struct feature' contains a pointer to the array that declares each
feature, followed by the number of entries in the array. The pointer
-can be NULL and the the size zero for any feature that is not present in
+can be NULL and the size zero for any feature that is not present in
the module. For example, to register only builtins in zsh and thereby
make them visible to the user, the structure should contain
"bintab" where the array is declared as an array of struct builtin,
@@ -483,7 +483,7 @@ tokenized. There are three helper functions available:
- int cond_match(args, num, str)
Again, the first two arguments are the same as for the other
functions. The third argument is any string. The result of the
- function is non-zero if the the num'th string from the array taken
+ function is non-zero if the num'th string from the array taken
as a glob pattern matches the given string.
Parameters
@@ -528,7 +528,7 @@ see the description of the following functions in the `params.c' file:
Note that if one defines parameters using the last two macros (for
scalars and arrays), the variable holding the value should be
-initialized to either `NULL' or to a a piece of memory created with
+initialized to either `NULL' or to a piece of memory created with
`zalloc()'. But this memory should *not* be freed in the
finish-function of the module because that will be taken care of by
the `deleteparamdefs()' function described below.