Fix typos

deining · deining · commit d5467fa812fe · 2025-09-10T22:21:10.000+02:00
diff --git a/content/advisories/grafanaloki.md b/content/advisories/grafanaloki.md
@@ -23,7 +23,7 @@ IE, your full start line may look like:
 
 `memcached -m 6000 -I 2m -o ext_path=/disk/extstore:500G,ext_wbuf_size=32,ext_threads=10,ext_max_sleep=10000,slab_automove_freeratio=0.10,ext_recache_rate=0`
 
-*Please set -m and ext_path appropraitely for your system*. Leave some RAM for
+*Please set -m and ext_path appropriately for your system*. Leave some RAM for
 your system to breathe and a little disk space overhead.
 
 Please use version 1.6.21 or newer as it improves the extstore write speed and
diff --git a/content/features/flashstorage.md b/content/features/flashstorage.md
@@ -179,7 +179,7 @@ some amount of time.
 
 For example, if you only store objects with TTL's of 86400 (about a day) or
 2400s. If you set `ext_low_ttl` to 2400 or higher, all of the latter objects
-will get stuck together. Once all of those objets have expired, the page they
+will get stuck together. Once all of those objects have expired, the page they
 were in is reclaimed entirely. This avoids holes and compaction necessary if
 placed alongside the longer TTL'ed objects.
 
@@ -276,11 +276,11 @@ Compaction however does require rewriting pages. More details of that is in doc/
 
 `-o ext_path=/data/file:5G` this is enough to get you started. See `memcached --help` for other options. This wiki will update with more details on what the options do, but most users should be able to use a minimal subset of options. If you have a very high performance setup, feel free to reach out and we can walk you through a configuration.
 
-The above creates an external cache of 5 gigabytes. Due to how the shim works, you wil not be able to actually store 5 gigabytes due to fragmentation over time. Background jobs will attempt to keep fragmentation in check.
+The above creates an external cache of 5 gigabytes. Due to how the shim works, you will not be able to actually store 5 gigabytes due to fragmentation over time. Background jobs will attempt to keep fragmentation in check.
 
 ## How safe is this really?
 
-I test pretty aggressively while developing features. The general stability of memcached should attest to a high quality. This feature is still in an experimental tages, but has had a good amount of baking time for the operations it does support. Keep in mind that many features are disabled for items sent to disk (incr/decr/append/prepend)
+I test pretty aggressively while developing features. The general stability of memcached should attest to a high quality. This feature is still in an experimental stage, but has had a good amount of baking time for the operations it does support. Keep in mind that many features are disabled for items sent to disk (incr/decr/append/prepend)
 
 ---
 
@@ -673,7 +673,7 @@ The slab page balancer has an algorithm specific for extstore configurations.
 
 For reference, [a python](https://github.com/memcached/memcached/blob/master/scripts/memcached-automove-extstore) and [internal C version](https://github.com/memcached/memcached/blob/master/slab_automove_extstore.c) of the algorithm exist.
 
-When tuning changes to the algoritm, it's easy to disable the internal
+When tuning changes to the algorithm, it's easy to disable the internal
 algorithm and use external scripts.
 
 Since the extstore system is designed to send items to storage before they're
diff --git a/content/features/proxy/api-reference.md b/content/features/proxy/api-reference.md
@@ -76,7 +76,7 @@ The first stage is to call `mcp_config_pools` from the "configuration thread".
 This stage defines backends and organizes them into pools. It is also a good
 place to decide on how keys and commands should be routed. A table tree of
 information is then returned from this function. The proxy is not blocked or
-otherise impacted while this function runs.
+otherwise impacted while this function runs.
 
 The second stage is to call `mcp_config_routes` from each "worker thread".
 These VM's run independently for performance reasons: there is no locking
@@ -200,7 +200,7 @@ using a scripting language to process requests.
 -- slot, further improving performance. It also lets all slots share internal
 -- references to pools and backends.
 
--- This function is excuted during the second stage, on every worker thread.
+-- This function is executed during the second stage, on every worker thread.
 -- The `t` argument is the table that was returned by the _conf function.
 -- All information needed to generate this handler _must_ be contained in this
 -- table. It is bad form to reach for global variables at this stage.
@@ -704,7 +704,7 @@ mcp.pool({backend1, backend2, etc}, {
     -- [TODO: add anchor for details]
     iothread = true|false,
 
-    -- If supplied this prefix will be added to the lables of all specified
+    -- If supplied this prefix will be added to the labels of all specified
     -- backends. This means this pool object will get unique TCP sockets for
     -- its backends. Usable for dedicating different sockets for different
     -- purposes (gets vs sets).
diff --git a/content/features/proxy/examples.md b/content/features/proxy/examples.md
@@ -297,7 +297,7 @@ temporarily rerouting cache requests while a server is failed. We do this first
 
 Next, if a request has failed over, we adjust the TTL of any 'set' commands
 to be lower. In this example we use five minutes. This prevents cache
-entires that have "failed over" from staying around for a long period of
+entries that have "failed over" from staying around for a long period of
 time, which can cause issues if server 'b' repeatedly fails.
 
 The short cache time should allow a good hit rate for objects which are
@@ -312,13 +312,13 @@ Q&A:
   - This will depend on your needs. Please contact us if you have questions
   here.
 - How do we handle backends that are flapping (ie; sometimes timing out but
-  not competely dead?
+  not completely dead?
   - You can adjust "anti flap" settings, which will force a backend to
   stay down with a backoff algorithm:
 ```lua
 settings{
   backend_flap_time = 30, -- stable for 30 seconds means not flapping
-  backend_flap_backoff_ramp = 1.2, -- multipler for backoff wait time
+  backend_flap_backoff_ramp = 1.2, -- multiplier for backoff wait time
   backend_flap_backoff_max = 3600, -- try at least once an hour
 }
 ```
diff --git a/content/features/proxy/infrastructure.md b/content/features/proxy/infrastructure.md
@@ -4,7 +4,7 @@ date = 2024-09-01T09:08:32-07:00
 weight = 50
 +++
 
-This page provides illustraed examples of ways that you can create load-balanced, multiple-node cacheing systems using the Memcached built-in proxy. For a general overview of the built-in proxy, see [Built-in proxy]({{<proxy_base_path>}}).
+This page provides illustraed examples of ways that you can create load-balanced, multiple-node caching systems using the Memcached built-in proxy. For a general overview of the built-in proxy, see [Built-in proxy]({{<proxy_base_path>}}).
 
 The memcached proxy is a flexible and lightweight system with few
 dependencies. Any memcached binary can be a proxy, a cache server, or both.
diff --git a/content/features/proxy/reference.md b/content/features/proxy/reference.md
@@ -221,7 +221,7 @@ cmdmap {
 Replace the following:
 
 * <var>COMMAND</var>: a Memcached command—for example, `set`. For a command list, see [Basic Text Protocol](/protocols/basic/).
-* <var>ROUTE_HANDLER</var>: a full route-handler defnition—for example, `route_direct{ [...] }`.
+* <var>ROUTE_HANDLER</var>: a full route-handler definition—for example, `route_direct{ [...] }`.
 
 You can use a `cmdmap{}` call in your configuration file in any place where a route handler call is valid. The following example `map{}` block defines a route that proxy uses only for keys with the prefix `main` and the command `set`:
 
diff --git a/content/protocols/meta.md b/content/protocols/meta.md
@@ -425,7 +425,7 @@ hi
 EX
 ```
 
-The above could be the result of a race condition: two proceses are trying to
+The above could be the result of a race condition: two processes are trying to
 move the data from version 72 to 73 at the same time. Since the underlying
 version is already 73, the second command will fail.
 
diff --git a/content/releasenotes/ReleaseNotes141.md b/content/releasenotes/ReleaseNotes141.md
@@ -14,7 +14,7 @@ This is a maintenance release consisting primarily of bug fixes.
 
 ### Fixes
 
-#### Criticial Fixes
+#### Critical Fixes
 
   * Boundary condition during pipelined decoding caused crash (bug72)
   * Bad initialization during buffer realloc (bug77)
diff --git a/content/releasenotes/ReleaseNotes1420.md b/content/releasenotes/ReleaseNotes1420.md
@@ -22,7 +22,7 @@ being blind for a few weeks.
 
 ### Fixes
 
-  * Fix a race condition causing new connections to appear closed, causing an inifinte loop.
+  * Fix a race condition causing new connections to appear closed, causing an infinite loop.
 
 
 ### New Features
diff --git a/content/releasenotes/ReleaseNotes1430.md b/content/releasenotes/ReleaseNotes1430.md
@@ -14,7 +14,7 @@ Bugfix release, with a critical fix to large item support.
 
   * Add MemoryDenyWriteExecute to the systemd service
   * Handle end of line comment on memcached.conf
-  * Add missing parameters and escape hypens as minus to manpage
+  * Add missing parameters and escape hyphens as minus to manpage
   * Modernize unit file in systemd
   * crawler now uses rate limiter sleeps properly (CPU overusage)
   * add slab_chunk_max to `stats settings`
diff --git a/content/releasenotes/ReleaseNotes1435.md b/content/releasenotes/ReleaseNotes1435.md
@@ -51,7 +51,7 @@ segmented LRU. With the "lru" ASCII command you can tune settings live, or
 even switch between algorithms entirely!
 
 So long as memcached is started with `-o modern` or similar, you can
-experiment with the hit ratio of differnt algorithms or options without
+experiment with the hit ratio of different algorithms or options without
 restarting with a cold cache each time.
 
 IE: `lru mode flat` to switch back from segmented. Or `lru mode segmented` to
diff --git a/content/releasenotes/ReleaseNotes1438.md b/content/releasenotes/ReleaseNotes1438.md
@@ -41,7 +41,7 @@ still evict, over time 3 will still become starved.
 
 This new algorithm attempts to keep the youngest evicting slab class to within
 80% of the age of the oldest slab class (by default). Ages are averaged over a
-window to avoid ping-ponging memory between slab classe.
+window to avoid ping-ponging memory between slab classes.
 
 It also still aggressively frees memory if too much is free.
 
diff --git a/content/releasenotes/ReleaseNotes148.md b/content/releasenotes/ReleaseNotes148.md
@@ -65,7 +65,7 @@ new connections. When this happens, connections will sit in the listen backlog
 close off, memcached will starts accepting new connections again and they will
 be served.
 
-This is undesireable as it can cause clients to delay or timeout for a long
+This is undesirable as it can cause clients to delay or timeout for a long
 period of time. Long enough that it may be quicker to treat the items as a
 cache miss.
 
@@ -92,7 +92,7 @@ There is also a new option for setting the size of the hash table on startup:
 ```$ memcached -o hashpower=20}}}
 
 If you run instances with many millions of items, and items are added very
-rapidly on a restart, it may be desireable to _presize_ the hash table.
+rapidly on a restart, it may be desirable to _presize_ the hash table.
 Normally memcached will dynamically grow the hash table as needed, and this
 operation is generally very low overhead. If you put decals on your '96 Mazda
 grapefruit shootermobile, you may like this option.
diff --git a/content/releasenotes/ReleaseNotes1515.md b/content/releasenotes/ReleaseNotes1515.md
@@ -11,7 +11,7 @@ http://www.memcached.org/files/memcached-1.5.15.tar.gz
 A couple small bugfixes, and two notable changes. An authentication mode for
 ASCII protocol, and removal of a minor feature flag.
 
-`-o inline_ascii_response` was a compatability mode which was disabled since
+`-o inline_ascii_response` was a compatibility mode which was disabled since
 1.5.0; it uses 10-20 more bytes of memory to speed up ASCII responses. Since
 we switched from snprintf to a fast itoa implementation years ago it was disabled by
 default. Now the option is gone.
diff --git a/content/releasenotes/ReleaseNotes153.md b/content/releasenotes/ReleaseNotes153.md
@@ -16,7 +16,7 @@ Bugfix release. Adds "GAT" command from binprot to asciiprot.
   * pledge privdropping support for OpenBSD
   * make for loop more clear in logger watcher
   * fix theoretical leak in process_bin_stat
-  * fix use of unitialized array in lru_maintainer
+  * fix use of uninitialized array in lru_maintainer
   * -o no_hashexpand to disable hash table expansion
   * fix chunked items set in binprot, read from ascii
 
diff --git a/content/releasenotes/ReleaseNotes1613.md b/content/releasenotes/ReleaseNotes1613.md
@@ -13,7 +13,7 @@ fix for large text multigets in certain conditions, and a rare slowdown in
 extstore.
 
 Also included in the codebase is a non production ready test version of an
-integrated proxy. For adventerous developers see `t/proxy.t` test code and the
+integrated proxy. For adventurous developers see `t/proxy.t` test code and the
 lua libraries at https://github.com/memcached/memcached-proxylibs - for
 everyone else, hold on for future versions.
 
diff --git a/content/releasenotes/ReleaseNotes1614.md b/content/releasenotes/ReleaseNotes1614.md
@@ -8,7 +8,7 @@ http://www.memcached.org/files/memcached-1.6.14.tar.gz
 
 ### Overview
 
-Montly bugfix release. Important fix if you happen to have a couple billion
+Monthly bugfix release. Important fix if you happen to have a couple billion
 items in a single instance. A handful of useful fixes and a bunch of updates
 to the upcoming proxy feature.
 
diff --git a/content/releasenotes/ReleaseNotes1618.md b/content/releasenotes/ReleaseNotes1618.md
@@ -10,7 +10,7 @@ http://www.memcached.org/files/memcached-1.6.18.tar.gz
 
 Mostly fixes and improvements to proxy mode.
 
-Meta protocol has some adjusments: extra spaces were being returns in a few
+Meta protocol has some adjustments: extra spaces were being returns in a few
 instances. If your client is looking for an exact number of spaces in meta
 responses please take note. We regret the error.
 
diff --git a/content/releasenotes/ReleaseNotes1626.md b/content/releasenotes/ReleaseNotes1626.md
@@ -9,7 +9,7 @@ http://www.memcached.org/files/memcached-1.6.26.tar.gz
 ### Overview
 
 Fixes a crash when `lru_crawler metadump` is used and the client connection is
-closed early. Requires closing the client excactly before the last few
+closed early. Requires closing the client exactly before the last few
 kilobytes of a dump are about to be flushed.
 
 Also improves the ergonomics of proxy configurations via start arguments.
diff --git a/content/releasenotes/ReleaseNotes169.md b/content/releasenotes/ReleaseNotes169.md
@@ -22,7 +22,7 @@ helped test this release!
   * extstore: use fcntl locking on disk file
   * portability fix for getsubopt
   * illumos build fixes + require libevent2
-  * core: generalize extstore's defered IO queue
+  * core: generalize extstore's deferred IO queue
   * fix connection limit tests
   * logger: fix spurious watcher hangups
   * watcher.t: reduce flakiness
diff --git a/content/serverguide/configuring.md b/content/serverguide/configuring.md
@@ -45,7 +45,7 @@ Since 1.5.6 memcached defaults to listening only on TCP. `-l` allows you to bind
 
 ### Unix Sockets
 
-If you wish to restrict a daemon to be accessable by a single local user, or just don't wish to expose it via networking, a unix domain socket may be used. `-s <file>` is the parameter you're after. If enabling this, TCP/UDP will be disabled.
+If you wish to restrict a daemon to be accessible by a single local user, or just don't wish to expose it via networking, a unix domain socket may be used. `-s <file>` is the parameter you're after. If enabling this, TCP/UDP will be disabled.
 
 ## Connection Limit
 
diff --git a/content/serverguide/maintenance.md b/content/serverguide/maintenance.md
@@ -101,7 +101,7 @@ The latter can show poor hitrates, as many get_misses are accounted for by this
 
 ## OS Health (avoid swap!)
 
-Memcached interacts hard with the network and with RAM. It's common for people to monitor swap usage, which can cause severe performance degredation to memcached.
+Memcached interacts hard with the network and with RAM. It's common for people to monitor swap usage, which can cause severe performance degradation to memcached.
 
 It's also important to watch your network stack. Linux, for example, sports a number of counters for its network interfaces related to dropped packets, underruns, crc errors, etc. Most switches also have per-port counters on packet issues or link issues. Degraded performance could trace down to bad wiring, bad switchport, a dying NIC, or a network driver in need of tuning.
 
@@ -111,4 +111,4 @@ Most minor releases of memcached focus on fixing bugs and adding instrumentation
 
 Minor features may show up as well. SASL authentication support happened in the mid-1.4 series, but the change is isolated and should not break existing clients.
 
-You should follow new releases and the release notes. It's often better to uprade early so you have the extra instrumentation when you need it, instead of wishing you had it when things go wrong.
+You should follow new releases and the release notes. It's often better to upgrade early so you have the extra instrumentation when you need it, instead of wishing you had it when things go wrong.
diff --git a/content/serverguide/performance.md b/content/serverguide/performance.md
@@ -114,7 +114,7 @@ every few years.
 
 Memory assigned via the `-m` commandline argument to memcached is reserved for item data storage. The primary storage is broken up (by default) into 1 megabyte pages. Each `page` is then assigned into `slab classes` as necessary, then cut into chunks of a specific size for that `slab class`.
 
-Once a page is assigned to a class, it is *never* moved. If your access patterns end up putting 80% of your pages in class 3, there will be less memory available for class 4. The best way to think about this is that memcached is actually many smaller individaul caches. Each class has its own set of statistical counters, and its own LRU.
+Once a page is assigned to a class, it is *never* moved. If your access patterns end up putting 80% of your pages in class 3, there will be less memory available for class 4. The best way to think about this is that memcached is actually many smaller individual caches. Each class has its own set of statistical counters, and its own LRU.
 
 Classes, sizes, and chunks are shown best by starting up memcached with `-vv`:
 
diff --git a/content/tutorialcachingstory.md b/content/tutorialcachingstory.md
@@ -77,7 +77,7 @@ So again, he takes keys that the Programmer uses and looks for them on his memca
 
 "But wait", he thinks "I gave each memcached 1 gigabyte of memory, and that means, in total, I can cache three gigabytes of my database, instead of just ONE! Oh man, this is great," he thinks. "This'll save me a ton of cash. Brad Fitzpatrick, I love your ass!"
 
-"But hmm, the next problem, and this one's a puzzler, this webserver right here, this one runing memcached it's old, it's sick and needs to be upgraded. But in order to do that I have to take it offline! What will happen to my poor memcache cluster? Eh, let's find out," he says, and he shuts down the box. Now he looks at his graphs. "Oh noes, the DB load, it's gone up in stride! The load isn't one, it's now two. Hmm, but still tolerable. All of the other memcacheds are still getting traffic. This ain't so bad. Just a few cache misses, and I'm almost done with my work. So he turns the machine back on, and puts memcached back to work. After a few minutes, the DB load drops again back down to 1, where it should always be.
+"But hmm, the next problem, and this one's a puzzler, this webserver right here, this one running memcached it's old, it's sick and needs to be upgraded. But in order to do that I have to take it offline! What will happen to my poor memcache cluster? Eh, let's find out," he says, and he shuts down the box. Now he looks at his graphs. "Oh noes, the DB load, it's gone up in stride! The load isn't one, it's now two. Hmm, but still tolerable. All of the other memcacheds are still getting traffic. This ain't so bad. Just a few cache misses, and I'm almost done with my work. So he turns the machine back on, and puts memcached back to work. After a few minutes, the DB load drops again back down to 1, where it should always be.
 
 "The cache restored itself! I get it now. If it's not available it just means a few of my requests get missed. But it's not enough to kill me. That's pretty sweet."
 
diff --git a/content/userguide/faq.md b/content/userguide/faq.md
@@ -31,7 +31,7 @@ All operations should run in O(1) time. They must be atomic. This doesn't necess
 
 ### Why is memcached not recommended for sessions? Everyone does it!
 
-If a session disappears, often the user is logged out. If a portion of a cache disappears, either due to a hardware crash or a simple software upgrade, it should not cause your users noticable pain. [This overly wordy post](http://dormando.livejournal.com/495593.html) explains alternatives. Memcached can often be used to reduce IO requirements to very very little, which means you may continue to use your existing relational database for the things it's good at.
+If a session disappears, often the user is logged out. If a portion of a cache disappears, either due to a hardware crash or a simple software upgrade, it should not cause your users noticeable pain. [This overly wordy post](http://dormando.livejournal.com/495593.html) explains alternatives. Memcached can often be used to reduce IO requirements to very very little, which means you may continue to use your existing relational database for the things it's good at.
 
 Like keeping your users from being knocked off your site.
 
diff --git a/content/userguide/usecases.md b/content/userguide/usecases.md
