aboutsummaryrefslogtreecommitdiff
path: root/spec/dos-spec/memory-exhaustion.md
diff options
context:
space:
mode:
Diffstat (limited to 'spec/dos-spec/memory-exhaustion.md')
-rw-r--r--spec/dos-spec/memory-exhaustion.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/spec/dos-spec/memory-exhaustion.md b/spec/dos-spec/memory-exhaustion.md
index 2cc55eb..14c1f6b 100644
--- a/spec/dos-spec/memory-exhaustion.md
+++ b/spec/dos-spec/memory-exhaustion.md
@@ -23,7 +23,7 @@ or derived from a fraction of the total amount of system RAM.
As of Tor 0.4.7.x, the MaxMemInQueues mechanism tracks the following
kinds of allocation:
-- Cells queued on circuits.
+- Relay cells queued on circuits.
- Per-connection read or write buffers.
- On-the-fly compression or decompression state.
- Half-open stream records.
@@ -59,7 +59,7 @@ oldest data. (For example, a circuit on which a single cell has
been queued for 5 minutes would be freed before a circuit where 100
cells have been queued for 5 seconds.) "Data queued on a circuit"
includes all data that we could drop if the circuit were destroyed:
-not only the cells on the circuit's cell queue, but also any bytes
+not only the cells on the circuit's relay cell queue, but also any bytes
queued in buffers associated with streams or half-stream records
attached to the circuit.