summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorthegoofist <49315797+thegoofist@users.noreply.github.com>2019-08-12 16:51:49 -0500
committerGitHub <noreply@github.com>2019-08-12 16:51:49 -0500
commitdd377994bb9700bb0f1672b3b6d9bba2fe09b867 (patch)
tree440c8ee2bb46832adca6ba58877498d99f129857
parent9955b59b4e1ede1965485e6b9a3ed3bd7fc68757 (diff)
Update README.org
-rw-r--r--README.org8
1 files changed, 4 insertions, 4 deletions
diff --git a/README.org b/README.org
index 3577dc7..afe3624 100644
--- a/README.org
+++ b/README.org
@@ -42,12 +42,12 @@
general purpose code.
Support for rewinding streams is enabled by logging reads to the stream. As
- you might imagine, logging every read can take can begin to take its toll
+ you might imagine, logging every read can begin to take its toll
on the memory heap. Hence, freeing a checkpoint can signal to the stream
that it may be acceptable to discard the log. Internally, the log is freed
- whenever there are no checkpoints remaining and when any play back on the
- log has been exhausted - i.e. whenever the log is certain to be no longer
- needed.
+ whenever there are no checkpoints remaining and when any playback on the
+ log has been exhausted - i.e. whenever the system is certain that the log is
+ no longer needed.
NOTE: As it stands right now, rewinding a stream to a checkpoint will also
free that checkpoint and all checkpoints AFTER the rewind point.