Lagrange [release]

doc fix: page caching setting is in preferences > content in v1.16.5

=> 12a80533f12a3ca9ae585176fbbe73d5f2364a5a

diff --git a/res/about/help.gmi b/res/about/help.gmi
index cf2536fa..7f396dd4 100644
--- a/res/about/help.gmi
+++ b/res/about/help.gmi
@@ -121,7 +121,7 @@ When navigating to a new page, the old page is cached in memory. If you navigate
 
 The page cache is saved to a file when Lagrange is shut down so it can be restored on the next launch.
 
-Maximum size of the cache can be configured on the "Network" tab of Preferences. Note that the entire cache is kept in memory at runtime. When the cache fills up, the oldest and largest page content is removed — both factors contribute to the removal. You can set the maximum size to 0 to disable caching altogether, but that will also disable the page content quick search feature.
+Maximum size of the cache can be configured on the "Content" tab of Preferences. Note that the entire cache is kept in memory at runtime. When the cache fills up, the oldest and largest page content is removed — both factors contribute to the removal. You can set the maximum size to 0 to disable caching altogether, but that will also disable the page content quick search feature.
 
 ### 1.1.4 Opening links in a new tab
 
Proxy Information
Original URL
gemini://git.skyjake.fi/lagrange/release/cdiff/12a80533f12a3ca9ae585176fbbe73d5f2364a5a
Status Code
Success (20)
Meta
text/gemini; charset=utf-8
Capsule Response Time
63.953462 milliseconds
Gemini-to-HTML Time
0.179035 milliseconds

This content has been proxied by September (3851b).