summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSiddharth VP <siddharthvp@gmail.com>2022-01-01 00:29:58 +0530
committerSiddharth VP <siddharthvp@gmail.com>2022-01-09 21:59:57 +0530
commit8242e84f9d518c0c80499fa30cc95897465da60a (patch)
treed28701a9cd7944ce45e78a9fbe8a6b9b0a485fa8
parent77c3feac09049784cf60aa931ea9ec01c141e0f0 (diff)
Fix typos in docs
Change-Id: I5ccf296e0bd9afd8a82b620002346496cef18f0e
-rw-r--r--docs/Logger.md2
-rw-r--r--docs/database.md4
-rw-r--r--docs/deferred.txt2
-rw-r--r--docs/magicword.md2
4 files changed, 5 insertions, 5 deletions
diff --git a/docs/Logger.md b/docs/Logger.md
index b1c2b1051818..65205d706098 100644
--- a/docs/Logger.md
+++ b/docs/Logger.md
@@ -54,7 +54,7 @@ provided by the class describes a more feature rich logging configuration.
backed by the monolog logging library
* MediaWiki.Logger.Monolog.LegacyHandler: Monolog handler that replicates the
udp2log and file logging functionality of wfErrorLog()
-* MediaWiki.Logger.Monolog.WikiProcessor: Monolog log processer that adds host:
+* MediaWiki.Logger.Monolog.WikiProcessor: Monolog log processor that adds host:
wfHostname() and wiki: wfWikiID() to all records
# Globals
diff --git a/docs/database.md b/docs/database.md
index cb893a1d43d2..aee95b2e6af0 100644
--- a/docs/database.md
+++ b/docs/database.md
@@ -58,7 +58,7 @@ To avoid excessive lag, queries which write large numbers of rows should be spli
## Working with lag
-Despite our best efforts, it's not practical to guarantee a low-lag environment. Lag will usually be less than one second, but may occasionally be up to 30 seconds. For scalability, it's very important to keep load on the primary low, so simply sending all your queries to the masprimaryter is not the answer. So when you have a genuine need for up-to-date data, the following approach is advised:
+Despite our best efforts, it's not practical to guarantee a low-lag environment. Lag will usually be less than one second, but may occasionally be up to 30 seconds. For scalability, it's very important to keep load on the primary low, so simply sending all your queries to the primary is not the answer. So when you have a genuine need for up-to-date data, the following approach is advised:
1) Do a quick query to the primary for a sequence number or timestamp
2) Run the full query on the replica and check if it matches the data you got
@@ -86,7 +86,7 @@ Instead of locking reads, combine your existence checks into your write queries,
## Query groups
-MediaWiki supports database query groups, a way to indicate a preferred group of database hosts to use for a given query. Query groups are only supported for connections to child (non-primary) databases, making them only viable for read operations. It should be noted that using query groups does not _guarantee_ a given group of hosts will be used, but rather that the query prefers such group. Making use of query groups can be benficial in many cases.
+MediaWiki supports database query groups, a way to indicate a preferred group of database hosts to use for a given query. Query groups are only supported for connections to child (non-primary) databases, making them only viable for read operations. It should be noted that using query groups does not _guarantee_ a given group of hosts will be used, but rather that the query prefers such group. Making use of query groups can be beneficial in many cases.
One benefit is a reduction of cache misses. Directing reads for a category of queries (e.g. all logging queries) to a given host can result in more deterministic and faster performing queries.
diff --git a/docs/deferred.txt b/docs/deferred.txt
index 9a62fda92a21..a472fcc806f7 100644
--- a/docs/deferred.txt
+++ b/docs/deferred.txt
@@ -4,7 +4,7 @@ A few of the database updates required by various functions here can be
deferred until after the result page is displayed to the user. For example,
updating the view counts, updating the linked-to tables after a save, etc. PHP
does not yet have any way to tell the server to actually return and disconnect
-while still running these updates (as a Java servelet could), but it might have
+while still running these updates (as a Java servlet could), but it might have
such a feature in the future.
We handle these by creating a deferred-update object and putting those objects
diff --git a/docs/magicword.md b/docs/magicword.md
index e57c30986e8a..f0270266cb7d 100644
--- a/docs/magicword.md
+++ b/docs/magicword.md
@@ -78,7 +78,7 @@ class MyExtensionHooks {
}
```
-- Online documentation (contains more informations):
+- Online documentation (contains more information):
- Magic words: <https://www.mediawiki.org/wiki/Manual:Magic_words>
- Variables: <https://www.mediawiki.org/wiki/Manual:Variable>
- Parser functions: <https://www.mediawiki.org/wiki/Manual:Parser_functions>