+The history and caching strategy in Elpher is extremely simple, but
+may be confusing without a good mental model of how it works. That
+is what this section attempts to provide.
+
+Essentially, @strong{every} time you navigate to a new page, either
+by clicking or pressing @key{RET} on a link, using @key{g} to jump
+to a new page by its address, or using @key{O} to open the root selector,
+the following two things occur:
+
+@enumerate
+@item
+the cursor position and content for the original page are recorded in an
+in-memory cache, and
+
+@item
+the original page is set as the ``parent'' of the new page.
+@end enumerate
+
+The only way to return to pages in this history is by using @key{u},
+which returns to the previous of the current page.
+@footnote{The addition of the new page to the history happens even if
+the new page is one that has been seen before. This is mostly the
+desired behaviour. However, opening an explicit ``back'' link provided
+by a gopher menu will also add a new entry to the history. Unless you
+haven't yet visited that menu, it's therefore better to use @key{u} to
+go back in this case.}
+
+One aspect that may seem peculiar is that Elpher lacks a corresponding ``next'' or
+``forward'' command. However, since Elpher caches the position of point,
+this will be automatically positioned on the link that was most recently followed
+from a given page. This means that, at least for links followed from menus
+and text files, the inverse of @key{u} is actually just @key{RET}.
+