MTSR/minetest_modding_book
4
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Formspecs: Fix spelling of features

Browse Source
This commit is contained in:
rubenwardy 2023-01-27 13:54:49 +00:00
parent 46a909aae7
commit 7cf48f5132
2 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
Gemfile
View File

@ -6,4 +6,5 @@ gem "webrick"
group :jekyll_plugins do group :jekyll_plugins do
gem "jekyll-sitemap" gem "jekyll-sitemap"
gem "jekyll-redirect-from" gem "jekyll-redirect-from"
gem "jekyll-sass-converter", "~> 2.0"
end end

8
_en/players/formspecs.md
View File

@ -100,7 +100,7 @@ settings of the client. Here's a formspec which is `2,2` in size:
Notice how we explicitly defined the formspec language version. Notice how we explicitly defined the formspec language version.
Without this, the legacy system will instead be used instead - which will Without this, the legacy system will instead be used instead - which will
prevent the use of consistent element positioning and other new feautures. prevent the use of consistent element positioning and other new features.
The position and anchor elements are used to place the formspec on the screen. The position and anchor elements are used to place the formspec on the screen.
The position sets where on the screen the formspec will be, and defaults to The position sets where on the screen the formspec will be, and defaults to
@ -225,9 +225,9 @@ may need to work on multiple forms, or on all forms.
The `fields` parameter to the function is a table of the values submitted by the The `fields` parameter to the function is a table of the values submitted by the
user, indexed by strings. Named elements will appear in the field under their own user, indexed by strings. Named elements will appear in the field under their own
name, but only if they are relevent for the event that caused the submission. name, depending on the event. Some elements will only be submitted if they caused
For example, a button element will only appear in fields if that particular button the event, such as buttons, and some elements will always appear in submissions,
was pressed. such as fields.
{% include notice.html notice=page.submit_vuln %} {% include notice.html notice=page.submit_vuln %}