mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2025-02-24 22:58:50 +01:00
fix easy typos
This commit is contained in:
parent
f181ad7c59
commit
834745929a
2 changed files with 3 additions and 3 deletions
|
@ -534,7 +534,7 @@ conn_update_on_close(conn_client_stats_t *stats, const tor_addr_t *addr)
|
|||
{
|
||||
/* Extra super duper safety. Going below 0 means an underflow which could
|
||||
* lead to most likely a false positive. In theory, this should never happen
|
||||
* but lets be extra safe. */
|
||||
* but let's be extra safe. */
|
||||
if (BUG(stats->concurrent_count == 0)) {
|
||||
return;
|
||||
}
|
||||
|
|
|
@ -2114,7 +2114,7 @@ static overload_onionskin_assessment_t overload_onionskin_assessment;
|
|||
|
||||
/**
|
||||
* We combine ntorv3 and ntor into the same stat, so we must
|
||||
* use this function to covert the cell type to a stat index.
|
||||
* use this function to convert the cell type to a stat index.
|
||||
*/
|
||||
static inline uint16_t
|
||||
onionskin_type_to_stat(uint16_t type)
|
||||
|
@ -2137,7 +2137,7 @@ onionskin_type_to_stat(uint16_t type)
|
|||
* the stats are reset back to 0 and the assessment time period updated.
|
||||
*
|
||||
* This is called when a ntor handshake is _requested_ because we want to avoid
|
||||
* to have an assymetric situation where requested counter is reset to 0 but
|
||||
* to have an asymmetric situation where requested counter is reset to 0 but
|
||||
* then a drop happens leading to the drop counter being incremented while the
|
||||
* requested counter is 0. */
|
||||
static void
|
||||
|
|
Loading…
Add table
Reference in a new issue