diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/HACKING/GettingStartedRust.md | 2 | ||||
| -rw-r--r-- | doc/HACKING/ReleaseSeriesLifecycle.md | 2 | ||||
| -rw-r--r-- | doc/HACKING/tracing/README.md | 4 | ||||
| -rw-r--r-- | doc/TUNING | 2 |
4 files changed, 5 insertions, 5 deletions
diff --git a/doc/HACKING/GettingStartedRust.md b/doc/HACKING/GettingStartedRust.md index adacf8afc2..beef825226 100644 --- a/doc/HACKING/GettingStartedRust.md +++ b/doc/HACKING/GettingStartedRust.md @@ -124,7 +124,7 @@ the module calls. Modules which call fewer other modules are better targets. Strive to change the C API as little as possible. -We are currently targetting Rust stable. (See `CodingStandardsRust.md` for more +We are currently targeting Rust stable. (See `CodingStandardsRust.md` for more details.) It is on our TODO list to try to cultivate good diff --git a/doc/HACKING/ReleaseSeriesLifecycle.md b/doc/HACKING/ReleaseSeriesLifecycle.md index e4068ed806..8536fbbd08 100644 --- a/doc/HACKING/ReleaseSeriesLifecycle.md +++ b/doc/HACKING/ReleaseSeriesLifecycle.md @@ -102,7 +102,7 @@ they do not apply to security-related patch release versions. 4. Open tickets for connecting the new branches to various other places. See section 2 above for a list of affected locations. -5. Stop running practracker on maintainence and release branches: +5. Stop running practracker on maintenance and release branches: * Remove "check-best-practices" from the check-local Makefile target in the maint-x.y.z branch only. * Delete the file scripts/maint/practracker/.enable_practracker_in_hooks diff --git a/doc/HACKING/tracing/README.md b/doc/HACKING/tracing/README.md index d9fb2e5341..f34709bf3a 100644 --- a/doc/HACKING/tracing/README.md +++ b/doc/HACKING/tracing/README.md @@ -47,7 +47,7 @@ A trace event in tor has the following standard format: tor_trace(subsystem, event_name, args...); ``` -The `subsystem` parameter is the name of the subsytem the trace event is in. +The `subsystem` parameter is the name of the subsystem the trace event is in. For example that could be "scheduler" or "vote" or "hs". The idea is to add some context to the event so when we collect them we know where it's coming from. @@ -135,7 +135,7 @@ This is pretty easy. Let's say you want to add a trace event in #include "lib/trace/events.h" ``` -Then, the `tor_trace()` macro can be used with the specific format detailled +Then, the `tor_trace()` macro can be used with the specific format detailed before in a previous section. As an example: ```c diff --git a/doc/TUNING b/doc/TUNING index 7da37e1adc..882a6dd68d 100644 --- a/doc/TUNING +++ b/doc/TUNING @@ -13,7 +13,7 @@ opened on your host at the same time. FreeBSD ------- -Tune the followind sysctl(8) variables: +Tune the following sysctl(8) variables: * kern.maxfiles - maximum allowed file descriptors (for entire system) * kern.maxfilesperproc - maximum file descriptors one process is allowed to use |