diff options
author | Samanta Navarro <ferivoz@riseup.net> | 2020-11-11 11:38:19 +0000 |
---|---|---|
committer | David Goulet <dgoulet@torproject.org> | 2020-11-12 11:44:09 -0500 |
commit | 4a0cd79588d2a472ab81e4f1d0e1e1bf6f2b390c (patch) | |
tree | 482e652a53ead4b26e8d97a4854671cdc0df0d61 /src/lib/fs | |
parent | e2d3c9c5f82a1369385dd99765c31ba479ba8f23 (diff) | |
download | tor-4a0cd79588d2a472ab81e4f1d0e1e1bf6f2b390c.tar.gz tor-4a0cd79588d2a472ab81e4f1d0e1e1bf6f2b390c.zip |
Fix typos.
Typos found with codespell.
Please keep in mind that this should have impact on actual code
and must be carefully evaluated:
src/core/or/lttng_circuit.inc
- ctf_enum_value("CONTROLER", CIRCUIT_PURPOSE_CONTROLLER)
+ ctf_enum_value("CONTROLLER", CIRCUIT_PURPOSE_CONTROLLER)
Diffstat (limited to 'src/lib/fs')
-rw-r--r-- | src/lib/fs/path.c | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/src/lib/fs/path.c b/src/lib/fs/path.c index 2eef4bded7..fc759f6169 100644 --- a/src/lib/fs/path.c +++ b/src/lib/fs/path.c @@ -180,7 +180,7 @@ clean_fname_for_stat(char *name) /** Modify <b>fname</b> to contain the name of its parent directory. Doesn't * actually examine the filesystem; does a purely syntactic modification. * - * The parent of the root director is considered to be iteself. + * The parent of the root director is considered to be itself. * * Path separators are the forward slash (/) everywhere and additionally * the backslash (\) on Win32. @@ -319,7 +319,7 @@ make_path_absolute(const char *fname) * picture explanation here should be read first. * * Purpose of the functions: - * - tor_glob - recevies a pattern and returns all the paths that result from + * - tor_glob - receives a pattern and returns all the paths that result from * its glob expansion, globs can be present on all path components. * - get_glob_opened_files - receives a pattern and returns all the paths that * are opened during its expansion (the paths before any path fragment that @@ -328,10 +328,10 @@ make_path_absolute(const char *fname) * allowed list. * * Due to OS API differences explained below, the implementation of tor_glob is - * completly different for Windows and POSIX systems, so we ended up with three - * different implementations: + * completely different for Windows and POSIX systems, so we ended up with + * three different implementations: * - tor_glob for POSIX - as POSIX glob does everything we need, we simply call - * it and process the results. This is completly implemented in tor_glob. + * it and process the results. This is completely implemented in tor_glob. * - tor_glob for WIN32 - because the WIN32 API only supports expanding globs * in the last path fragment, we need to expand the globs in each path * fragment manually and call recursively to get the same behaviour as POSIX |