diff options
Diffstat (limited to 'doc/dev/notes')
| -rw-r--r-- | doc/dev/notes/cell-lifecycle.md | 2 | ||||
| -rw-r--r-- | doc/dev/notes/service-side-pow.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/dev/notes/cell-lifecycle.md b/doc/dev/notes/cell-lifecycle.md index 88ce0b880..6b96c5c88 100644 --- a/doc/dev/notes/cell-lifecycle.md +++ b/doc/dev/notes/cell-lifecycle.md @@ -294,7 +294,7 @@ We continue reading from the stream, but we stop writing to it. 7. But reading from `input` means having to respond to the received cell, e.g. by sending a circuit-level SENDME. The other end won't receive our "response" though, - because our "response" cells will get queueud + because our "response" cells will get queued until our KIST Socket says it's ok to write some more However, when KIST-limiting kicks in, we don't expect to actually receive diff --git a/doc/dev/notes/service-side-pow.md b/doc/dev/notes/service-side-pow.md index 68850511c..9c154476d 100644 --- a/doc/dev/notes/service-side-pow.md +++ b/doc/dev/notes/service-side-pow.md @@ -20,7 +20,7 @@ Related spec docs: * Used nonces datastructure * Verifier for the correct seed (implies that access to the verifier should be keyed on `SeedHead` since that's all we have access to when processing a request, we don't know the TP) - * Total effort value, which must somehow be updated upon successful requets + * Total effort value, which must somehow be updated upon successful requests * At some point after we have verified the solve, the code dequeuing requests in order to send them to the backend that generates responses needs to be able to see the effort associated with that request. |