summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorashtrayoz <33517241+ashtrayoz@users.noreply.github.com>2017-12-10 23:56:01 +1100
committerparamat <mat.gregory@virginmedia.com>2017-12-10 14:30:37 +0000
commit02cc257fe09ee0a68f3c09e0cbe48cbbda29a71c (patch)
tree9ba3b793d04e0348ddd96010c20b757668f1e9e0
parent419799b8312244d6689b48e5fbdf8dd74b6cc7bd (diff)
downloadminetest-02cc257fe09ee0a68f3c09e0cbe48cbbda29a71c.tar.gz
minetest-02cc257fe09ee0a68f3c09e0cbe48cbbda29a71c.tar.bz2
minetest-02cc257fe09ee0a68f3c09e0cbe48cbbda29a71c.zip
Lua_api.txt: Fix a spelling error
-rw-r--r--doc/lua_api.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/lua_api.txt b/doc/lua_api.txt
index 1e6cf0b71..d3b493fc3 100644
--- a/doc/lua_api.txt
+++ b/doc/lua_api.txt
@@ -2382,7 +2382,7 @@ Strings that need to be translated can contain several escapes, preceded by `@`.
when translation. Due to how translations are implemented, the original translation string **must** have
its arguments in increasing order, without gaps or repetitions, starting from 1.
* `@=` acts as a literal `=`. It is not required in strings given to `minetest.translate`, but is in translation
- files to avoid begin confused with the `=` separating the original from the translation.
+ files to avoid being confused with the `=` separating the original from the translation.
* `@\n` (where the `\n` is a literal newline) acts as a literal newline. As with `@=`, this escape is not required
in strings given to `minetest.translate`, but is in translation files.
* `@n` acts as a literal newline as well.